Build your discovery layer
Make canonical pages easy to find and understand.
A sitemap is a discovery hint, not an indexing command. Canonical tags identify your preferred version of substantially similar pages; they are also hints. Structured data describes facts already visible to readers.
Your implementation route
Use Wix's page SEO settings for titles, descriptions, indexing and structured data. Inspect the sitemap exposed by the live site and submit its URL in Search Console. Check existing schema before adding another organization record.
Platform boundaries & account requirements
Use Wix's native integrations and SEO & GEO tools. Backend examples belong in a supported Wix backend module or an external service, never in a page embed.
Open Wix ↗Published canonical URL list, existing schema inspection and access to page SEO fields or templates.
Follow the steps
Check only after completingClean your URL inventory
Keep final, public, indexable, canonical URLs in the sitemap. Remove redirects, broken URLs, drafts and noindex pages. Use accurate lastmod dates for meaningful changes, not today's date on every request.
Set unique page metadata
Give each important page a specific title, a truthful description and an absolute canonical URL. Link to it from relevant navigable pages. Make location pages meaningfully specific, not copied city-name variations.
Add one consistent identity record
Inspect existing JSON-LD before adding more. Reuse a stable @id for the organization, align its name/URL with visible facts, and use a suitable type. Add real profile links only. Product and local business markup need their appropriate properties; do not invent ratings.
Submit and validate
Open the live sitemap, submit it in Search Console and watch processing/errors. Check rendered source and the Rich Results Test for supported types; a general Organization record may not produce a visible rich result. Validate actual facts as well as syntax.
Implementation recipes
Expand · choose · copy</>A small sitemapOpen recipe
Custom site: serve as /sitemap.xml with an XML content type. Managed hosts normally generate this for you.
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url><loc>https://example.com/</loc></url>
<url><loc>https://example.com/services/heat-pump-repair</loc></url>
</urlset>
<!-- Add lastmod only when you know the actual meaningful update date. --></>One consistent organization recordOpen recipe
Page head/body through a supported template/integration. Match visible facts and existing schema. This is Organization markup, not a complete local-business or product recipe.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Business",
"url": "https://example.com/",
"description": "Describe the real service, audience and market."
}
</script>The sitemap loads, its sample URLs are correct, and the page has one coherent canonical/identity setup. Record validation results and fix critical errors before release.
Restore the prior metadata/template or disable only the new schema owner. Avoid removing valid markup from an existing platform integration.
Read the primary instructions
Guidance checked October 7, 2026. “2027” describes this prototype’s visual concept, not a prediction of platform rules.