# Website verification and 8900 cleanup **Status: the new site is live. The IJ470 page is live. The IJ375 redirects with a client-side redirect; verify a true 301. The 8900 is no longer in the product sitemap.** Verified on Wednesday, November 4, 2026. This replaces the earlier website build plan. The page and the redirects already exist. The work now is verification plus two small fixes. --- ## 1. Current state, verified | Item | Result | |---|---| | IJ470 product page | Live at https://factronicsusa.com/product/linx-ij470 | | IJ375 URL | Client-side redirect to the IJ470 page. The response is a 200 page with a meta refresh, not an HTTP 301. Verify or add a true 301. | | 8900 product page | Not in the product sitemap. The old URL falls back to the homepage | | Standard Bots main | Live at https://factronicsusa.com/standard-bots | | Standard Bots Spark | Live at https://factronicsusa.com/standard-bots/spark | | Standard Bots Core | Live at https://factronicsusa.com/standard-bots/core | | Standard Bots Thor | Live at https://factronicsusa.com/standard-bots/thor | | Standard Bots Bolt | Live at https://factronicsusa.com/standard-bots/bolt | | Suppliers page | Live at https://factronicsusa.com/our-suppliers | --- ## 2. Fix 1. Add the 8900 redirect The 8900 no longer has a product page. The old URL currently falls back to the homepage. A 301 preserves old links and sends the visitor to the right product. 1. Log in at https://factronicsusa.com/wp-admin/ as an administrator. 2. Open Rank Math SEO, then Redirections. 3. Click Add New. 4. Source URL: `product/linx-8900` and `product/linx-8900-series/`. Add one rule for each if both exist. 5. Destination URL: `https://factronicsusa.com/product/linx-ij470/`. 6. Redirection Type: 301 Permanent. 7. Click Add Redirection. 8. Open each old URL in a private window. It must land on the IJ470 page in one hop. 9. Command line check: ```text curl -I https://factronicsusa.com/product/linx-8900 ``` Expected: `301 Moved Permanently` with a `Location` header for the IJ470 page. If the redirect does not fire, purge the caching plugin and the Cloudflare cache, then retest. ### 2b. Confirm the IJ375 redirect is a true 301 The old IJ375 URL currently returns a 200 page with a meta refresh. That works in a browser, but it is weaker for search engines than an HTTP 301. 1. Open a terminal and run: ```text curl -I https://factronicsusa.com/product/linx-ij375/ ``` 2. If the response is `301 Moved Permanently`, no change is needed. 3. If the response is `200 OK`, add a Rank Math redirect: - Rank Math SEO, Redirections, Add New. - Source URL: `product/linx-ij375`. - Destination URL: `https://factronicsusa.com/product/linx-ij470/`. - Redirection Type: 301 Permanent. - Add Redirection. 4. Purge the cache and run the curl check again. --- ## 3. Fix 2. Remove or answer the stale 8900 FAQ The IJ470 page has a leftover FAQ question, "Is the Linx 8900 still available?" The answer is not visible on the page. Choose one: ### Option A. Remove the question, recommended 1. Open the IJ470 page in Elementor or the block editor. 2. Find the FAQ block. 3. Delete the row for "Is the Linx 8900 still available?" 4. Update the page. 5. Open the live page and confirm the FAQ now ends cleanly. ### Option B. Answer the question 1. Open the IJ470 page in Elementor or the block editor. 2. Find the FAQ row. 3. Add this answer: ```text The Linx 8900 is no longer listed as a current product on this site. Linx states that the IJ470 replaces the IJ355 and the IJ375. If you are running an 8900, contact us and we will confirm the right path for your line. ``` 4. Update the page. 5. Open the live page and confirm the answer renders. --- ## 4. Verify the IJ470 page - [ ] H1 is `Linx IJ470 Large Character Inkjet Case Coder`. - [ ] The page returns 200 in a private window. - [ ] The primary call to action goes to https://meetings.hubspot.com/jovan-gutic. - [ ] The spec table renders on mobile and does not overflow. - [ ] The page names the IJ470 in every call to action. - [ ] There are no em dashes or en dashes. - [ ] There are no compliance claims. The page describes what the equipment does. - [ ] The "IJ375 is replaced" section is visible. - [ ] The stale 8900 FAQ is removed or answered. - [ ] The page appears in the product sitemap at https://factronicsusa.com/product-sitemap.xml. ## 5. Verify the redirects - [ ] `/product/linx-ij375` returns a true 301 to `/product/linx-ij470`, not a 200 page with a meta refresh. - [ ] `/product/linx-8900` returns a 301 to `/product/linx-ij470` after Fix 1. - [ ] `/product/linx-8900-series/` returns a 301 to `/product/linx-ij470` after Fix 1. - [ ] No old URL returns a 404. - [ ] No redirect chain is longer than one hop. ## 6. Verify the Standard Bots pages - [ ] Main page loads and links to Spark, Core, Thor, and Bolt. - [ ] Each product page names the robot correctly. - [ ] The homepage mentions Standard Bots. - [ ] The Our Suppliers page lists Standard Bots. - [ ] Every call to action goes to a working page. - [ ] No broken images. ## 7. Internal links and menu - [ ] Search the site for `ij375`. Update body links to point to `/product/linx-ij470/`. - [ ] Search the site for `8900`. Update links that point to the old product page to the IJ470 page or the Linx category. - [ ] Check the Linx 9800 Series page for a related products module that still lists the IJ375. - [ ] Check the Linx category page for an IJ375 card. - [ ] Check the footer and the menu for old links. - [ ] Confirm the menu has the IJ470 and does not have the IJ375. - [ ] Open every Linx item in the menu in a private window. No 404s. ## 8. Search Console and monitoring - [ ] Confirm the product sitemap includes the IJ470 and excludes the IJ375 and the 8900. - [ ] Submit the updated sitemap in Google Search Console. - [ ] Open Google Search Console, Pages, and check for new 404s in the 7 days after the change. - [ ] Open Rank Math, 404 Monitor. Confirm no new 404s from internal links. - [ ] Purge the caching plugin and the Cloudflare cache. - [ ] Re-test every URL in this file. ## 9. Rollback If a redirect or a page breaks: 1. Open Rank Math, Redirections, and disable the new rule. 2. Restore the previous page status if one was changed. 3. Purge the cache. 4. Retest the URL. The old content is not deleted. Nothing in this file requires deleting a page.