Neto SEO: product pages, categories and redirects
Improve Neto store SEO with product and category fields, clean redirects, template checks and a practical way to verify published changes.
- Published
- Last updated
Neto SEO starts with accurate product and category content, page-specific search fields and redirects that keep existing product links working. Check the published page after each change, because a saved field only helps when the storefront outputs it correctly.
For an established catalogue, start with one product and its category before applying the same changes in bulk. You’ll need permission to edit those records, access to the theme owner for template faults and a verified Search Console property for indexing checks.
Find Neto’s current SEO settings
Use Maropost’s Neto documentation for the control panel that runs your store. The support library contains Neto by Maropost and Maropost Commerce Cloud material, so match the documented screen to your own panel.
- Open Products > View Products and choose a product. Find its SEO section and record its existing search title, description and URL.
- Open the relevant category through Products > Product Categories. Record its name and descriptions, then inspect its SEO fields.
- Compare a record with blank SEO fields against one with explicit values. Note the site-wide title pattern, store-name suffix and description fallback in the published source.
- Ask the theme owner to identify the shared defaults before changing them. Keep product and category overrides where a page needs its own wording.
Maropost’s SEO metadata guide distinguishes the page title, meta description, page heading and canonical URL. These have different jobs. The title is separate from the visible heading, while the canonical identifies the preferred URL for duplicate versions.
For category content, Maropost documents Short Description 1 as the fallback for an empty SEO Meta Description. An existing override can therefore explain why changing the short description leaves the search description unchanged.
Improve product and category search content
Give the product its exact identity and give the category a useful purpose. Keep customer-visible content readable while writing each search field for the page it describes.
Consider a hypothetical parts retailer selling a replacement filter for a fictional Model HX200 mower. The supplier’s confirmed specification identifies the filter as part F17.
| Field or content | Example to enter | What it explains |
|---|---|---|
| Product name | F17 replacement air filter for Model HX200 | The item and its confirmed compatible model |
| Product description | Replacement filter for Model HX200. Supplied as one filter. Compare part F17 with your existing part before ordering. | Compatibility and pack contents |
| SEO Page Title | F17 air filter for Model HX200 | The specific product page |
| SEO Meta Description | Find the F17 replacement air filter for Model HX200. Check compatibility and pack contents before ordering. | The page’s useful purchase information |
| Category description | Compare mower air filters by model and part number. Open a product to check its listed compatibility. | How to choose within the range |
Replace the fictional details with verified supplier information. Avoid assigning the same compatibility text to every filter when the models differ.
Neto’s product field definitions separate SEO Page Title and SEO Meta Description from product data. Hidden Search Keywords support product searches within the store. They’re separate from SEO Meta Keywords, which Maropost recommends leaving empty.
Save the product and category, then open both public pages. Confirm that the descriptions appear where intended and the category links to the correct products. A populated field that the theme never displays leaves shoppers without that information.
Preserve product links during URL changes
Record the existing public URL before changing a product path, then test that the old address reaches its replacement through a permanent redirect.
- Open the product’s current public page and save its full address beside its SKU. Record any existing redirect destination too.
- In Products > View Products, open the product and select its SEO tab. Under Product URL, clear Automatically Update and enter the replacement path.
- Save the record. Inspect the old URL’s HTTP response and confirm that its 301 redirect points directly to the new product URL.
- Open the replacement independently. It must return HTTP 200 and display the intended product.
- Update category links and other links you control to use the replacement directly. Recheck any older redirects so they also reach the final destination without a chain.
Maropost’s URL-change instructions say individual page or product URL changes create a 301 automatically. They also warn that Regenerate URLs For All Products does not create those redirects. Before bulk regeneration, export the old product URLs and prepare the redirect import.
Manage redirects through Settings & Tools > All Settings & Tools > Webstore > 301 Redirects. Older documentation also names Marketing > SEO > 301 Redirects. Use the screen available in your panel, then verify its response from the public URL.
Inspect templates and catalogue feeds
Compare the saved fields with the rendered page before assuming a theme uses them. View Page Source for the document head and inspect the visible product heading in the browser.
Check the following output on the changed product and category:
- The document title and meta description use the intended values without repeated store-name suffixes.
- The visible main heading identifies the product or category correctly.
- The canonical points to the intended indexable URL, rather than a retired path or unrelated category.
- Product structured data describes the product shown, with price and availability matching the visible offer.
Run the product URL through Google’s Rich Results Test. Follow Google’s product structured-data guidance for purchasable product pages, including its merchant-listing requirements. A successful test establishes technical eligibility, not a promise of a rich result.
A shopping-channel feed is another output from the catalogue. Updating search metadata doesn’t establish that a feed’s title or destination URL changed. Google accepts product information through page markup and Merchant Center feeds, and can combine the two. Inspect the exported record separately. For that work, follow the product feed optimisation guide.
Confirm discovery after publishing
Check that the new URL is publicly accessible and included in the store’s discovery paths, then inspect it in Search Console.
- Open the page while signed out. For a missing product, check Active and Approved to show on Webstore in its record before investigating Google.
- Inspect robots directives and the canonical. A page intended for search must be accessible to Google without a login and must not carry a noindex instruction.
- Open the sitemap index and its relevant child sitemap. Neto’s sitemap setup guide gives the index path as
/sitemap_index.xml.gz. Confirm the replacement URL is listed. For categories, also inspect Visible On Sitemap. - If the sitemap is stale, locate System Scheduled Tasks through Settings & Tools > All Settings & Tools. Check the Site Map task and use Run Now to regenerate it.
- Use Search Console’s URL Inspection on the replacement. Compare its live test with the indexed version, including Google’s selected canonical. Request indexing after correcting any blockers.
When the admin shows new text but the public source shows old text, first confirm you edited the correct record and its active template. Retry with a browser reload that bypasses its cache. If output stays stale, ask the theme owner to inspect the field mapping and Neto’s Web Accelerator settings. Restore normal caching after design diagnostics.
Google’s sitemap guidance explains that inclusion helps discovery but doesn’t guarantee indexing. Its recrawl guidance also separates a request from inclusion in search. Finish the catalogue change when the old link redirects correctly, the replacement outputs the saved content and the live inspection can access it. Monitor the indexed result separately.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.