Study first
Review the ideas behind the questions
These notes cover the technical decisions that come after setup basics, especially when duplicate URLs, rendering, crawl efficiency, or validation are involved.
Canonical and redirect signals
Canonicalization is about choosing the URL that should represent duplicate or very similar content. Redirects and canonical annotations are stronger signals than sitemap inclusion, but they need to agree.
- Use a permanent redirect when a duplicate URL should no longer be used.
- Use rel=canonical when duplicate URLs need to remain accessible.
- Avoid sending conflicting canonical signals for the same page.
- Link internally to the canonical URL rather than to duplicate variants.
JavaScript rendering checks
JavaScript can change what Google sees. Important SEO signals should be present clearly, and rendered pages should still expose useful content, links, titles, and descriptions.
- Unique titles and meta descriptions should describe the rendered page.
- Links that matter for discovery should be crawlable.
- Avoid relying on fragile client-side changes for canonical clarity.
- Test rendered output when traffic-critical pages depend on JavaScript.
Crawl efficiency and status codes
Crawl diagnostics are practical when a site has many URLs, duplicate paths, faceted navigation, or unstable responses. The goal is to help crawlers spend time on useful URLs.
- Do not waste crawl time on duplicate or low-value URL patterns.
- Use stable success, redirect, not found, or temporary unavailable responses intentionally.
- A 404 or 410 is appropriate for a page that is truly gone.
- Use temporary server-error signals carefully when downtime is short-lived.
Structured data and validation
Structured data can help Google understand a page and enable rich results when the page qualifies, but it must match visible page content and follow feature guidelines.
- Use structured data on the page it describes.
- Do not add markup for content users cannot see.
- Validate structured data during development and after deployment.
- Structured data eligibility does not guarantee a rich result.