SEO reference notes

Crawlable links

Use real anchor elements with href URLs for navigable public content. Important documentation should have stable routes that return useful content directly. A button that only changes hidden application state is not an equivalent public document link.

Primary reference: developers.google.com

JavaScript and initial HTML

A JavaScript application can present little useful text in its initial HTML. Public documentation rendered as static HTML gives users and crawlers content without waiting for the chat application to initialize. Keep that content relevant and visible to users.

Primary reference: developers.google.com

Descriptive page metadata

Give each public page a concise title and description that match its actual purpose. Avoid repeating the same generic description across unrelated guides. Metadata helps describe a page; it is not a guarantee of a chosen search snippet or ranking.

Primary reference: developers.google.com

Canonical URLs

Use one consistent preferred URL for each public page and align canonical tags, sitemap entries and internal links. Canonicalization is a signal rather than access control. Verify hostname and redirect behavior on the deployed server.

Primary reference: developers.google.com

Sitemaps

A sitemap lists public URLs you want discovered, with accurate optional metadata. Keep private API routes, account-specific content and nonexistent URLs out of it. Listing a page does not guarantee that a search engine will index it.

Robots and indexing

robots.txt controls crawling behavior for cooperating crawlers. It should not be used as the sole method of preventing indexing or protecting private information. Separate crawl controls, noindex directives and actual access restrictions.

Primary reference: developers.google.com

Structured data accuracy

Structured data should describe the content and entities actually represented on the page. Do not fabricate reviews, ratings, prices, affiliations or capabilities. Validate JSON syntax and keep identifiers consistent across pages.

Useful content architecture

Group related questions into substantial guides with examples and clear navigation. Many near-duplicate pages are not a substitute for useful coverage. Organize around tasks the product actually supports.

Preview assets

Social preview metadata should point to an existing public image with an accurate description. Check the actual deployed image URL and dimensions. A metadata tag referencing a missing asset does not produce a usable preview.

SEO verification

Check the deployed page status, title, canonical, internal links, sitemap entries and asset responses. Search-engine indexing and ranking must be observed separately; passing a local HTML test does not establish search performance.