011. Make the source technically available
A system cannot retrieve a page it cannot reach or index.
- Return a successful status and expose critical content in initial HTML.
- Use one canonical URL, an accurate sitemap and deliberate robots controls.
- Keep preview hosts out of the index and avoid private application routes in public discovery files.
- Use responsive pages, descriptive links and accessible image text.
022. Make the entity and answer explicit
Clear identity reduces the risk that facts are attributed to the wrong organization.
- Use one official company name, domain, logo and contact set.
- State product ownership, status, pricing and limitations on authoritative pages.
- Answer real buyer questions immediately beneath descriptive headings.
- Use structured data to describe visible content, not to create hidden claims.
033. Support claims with retrievable evidence
Evidence gives search-connected systems more context for selecting and citing a source.
- Use genuine product screenshots and public application destinations.
- Publish factual project profiles without invented metrics or testimonials.
- Link to authoritative references for technical platform claims.
- Keep dates and facts current and document material changes.
044. Measure without overclaiming
Visibility and commercial impact are separate measurements.
- Use Search Console and Bing Webmaster data after a controlled deployment.
- Record cited pages or grounding queries when a platform exposes them.
- Measure qualified enquiries separately from impressions or citations.
- Treat absent referral data as unknown rather than inventing attribution.