A practical technical SEO guide to policy-aligned slugs, robots.txt, hreflang, FAQPage JSON-LD, and UTM governance.
Design stable URLs, canonicals, and redirects together
A slug can be concise and readable, but stability matters most. Changing a published URL merely for a better keyword can fragment links, bookmarks, and measurement. When change is necessary, the old URL needs a permanent redirect while canonical, internal links, sitemap, and hreflang update together.
Shared ASCII slugs across language folders are not a language error when each page has localized visible content. Every language page should canonicalize to itself and list the complete reciprocal alternate cluster.
- Check collisions before publishing.
- Keep old URLs in redirect tests.
- Exclude campaign parameters from canonicals.
- Use a self-canonical on every language version.
Robots.txt is not an indexing control
Robots.txt guides crawling; it does not reliably remove a URL from indexing. Protect sensitive content with access control, and use appropriate robots meta or HTTP headers for accessible pages that should not be indexed. An accidental root `Disallow: /` can hide an entire release from crawling.
Review every user-agent group and declare sitemaps with absolute HTTPS URLs. A structural checker cannot observe live CDN rules, response status, or page-level robots directives, so verify with Search Console URL Inspection.
Make hreflang clusters complete and reciprocal
Every language version must list itself and all alternatives using the same fully qualified cluster. `x-default` provides a fallback for unmatched languages. Correct locale codes are insufficient when alternate URLs redirect or canonicalize elsewhere.
Translating navigation while leaving the main content in one language is not full localization. Titles, descriptions, workbench labels, guidance, FAQs, and structured data should match the visible language.
- Use one canonical URL per localized page.
- Return HTTP 200 for every alternate.
- Keep clusters identical across versions.
- Test rendered head and sitemap output.
Keep FAQ markup and UTM measurement tied to visible truth
Every question and answer in FAQPage JSON-LD must also be visible on the canonical page. Structured data must represent the page's real purpose and must not invent reviews, ratings, or guarantees. Valid markup never guarantees a rich result or ranking.
UTM parameters describe measurement, not content variants. Standardize source, medium, and campaign names, never place personal data in them, and avoid UTM tags on ordinary internal links. Test host, query, fragment, and the analytics event before launch.
Sources and verification
The following primary and official documentation was checked for this guide. Review each source's current version and change date as well.
Content is checked against visible ByteQuant product behavior and the listed primary sources where available. It is general information, not legal or security advice.