Canonical: the preferred page address
Twicart’s canonical setup is designed with search-engine guidance in mind. A canonical identifies the preferred address among similar pages. Keeping page content and URL relationships consistent is an important part of technical SEO.
Category pagination is part of this approach. Google recommends a separate canonical URL for each paginated page showing different products. The URL structure should account for each page’s product listing rather than automatically treating page two as a copy of page one.
Automatic Schema: structured data built in
Sites built with Twicart include a Schema foundation. The system generates structured data appropriate to the page type, without requiring customers to write Schema code for each page. As you prepare product, category and content information, the system complements it with machine-readable data.
| Area | SEO approach |
|---|---|
| ItemPage | Describes the product page as a page about an item. |
| CollectionPage | Describes a category page as presenting a collection. |
| WebPage | Describes regular content pages as web pages. |
These types describe the page. ItemPage alone does not establish that all fields required for a Product rich result are present. Eligibility depends on the types and fields supported by the relevant Google feature.
The system handles repetitive Schema setup so you can focus on accurate, current content. Structured-data validation checks eligibility; it is not an overall SEO score. Google separately determines rich-result display.
Ready-to-use sitemap: /sitemap_index.xml
Access your Twicart sitemap by adding /sitemap_index.xml to your domain. Example format: https://your-site.com/sitemap_index.xml. Replace the example domain with your own.
A sitemap offers search engines another route to discover site URLs. A sitemap index lists sitemap files. After verifying your site in Search Console, submit this address and monitor processing.
A sitemap helps discover URLs; submitting it does not mean every page will be indexed immediately. Monitor indexing per page to assess content or access issues.
Ready-to-use product feed: /product-feed.xml
The product feed is available at /product-feed.xml on your domain. Example format: https://your-site.com/product-feed.xml. It presents product information as a data feed. The sitemap supports URL discovery, while the product feed supplies product data.
Accurate colour, dimensions and other core details in product management support feed quality. A ready feed does not automatically create an advertising account or guarantee product approval; the receiving service’s account and data requirements still apply.
Monitor SEO after publishing
- Review product and category content, metadata and indexing preferences.
- Open sitemap and product-feed URLs on your own domain.
- Monitor sitemap processing and important pages’ indexing in Search Console.
- Check structured data with the relevant validation tools.
- Keep SEO fields current as content and the catalogue change.
URL redirects and removed content
In Twicart, redirect a source URL to your chosen destination. Use 301 and other supported redirect methods for address changes, old campaign links and site migrations. A 301 signals a permanent move from the old URL to the new one.
Use a 410 response for permanently removed content with no replacement page. A 410 does not redirect to a destination; it states that the content is permanently gone. This lets you distinguish moving an address from removing content.
You can also manage redirect settings in bulk with Excel. This is useful in migrations where many old links need to be mapped to new addresses.
SEO control for filtered category URLs
SEO management covers category URLs produced by colour, size, price or sorting choices. Indexing preferences and canonical relationships for filtered URLs are considered alongside product browsing. Manage how these different views are presented to search engines.
Advanced product, variant, shipping and return Schema
Twicart’s structured data support extends beyond page types. Product and Offer describe information such as price, availability, SKU/EAN and brand; ProductGroup describes variant relationships. Connecting colour and size choices to their product family helps search engines understand the product structure.
Structured data support also covers shipping and returns. Delivery costs and times and return policies complement product and business information. Accurate, current product and policy details are important for the quality of automatically generated data.