SEO, SXO and visibility

Make content findable, understandable and useful across search engines, answer engines and conversion journeys.

61 articles · Latest article updated

Search covers every article in this topic, including the archive and article text.

Understand the topic

A practical guide to this topic

Useful visibility requires accessible pages, clear answers and an architecture that connects related subjects. This category examines indexing, search intent, structured data and the journey after discovery. A cyber page should explain its subject and scope before proposing an action. Visibility goes beyond impressions: verify that information is indexable, understandable, attributed and connected to a useful guide or contact. A citation in a generated answer remains a dated observation, distinct from a click or qualified enquiry.

What to examine
  • Verify access and rendering of important pages before adding refinements.
  • Cover a topic with sources, examples, limits and links to genuine subtopics.
  • Measure visibility, citations and useful actions separately.
  • Separate discovery, crawling, canonical selection and indexing in each diagnosis.
  • Give every old address a relevant decision and verify destinations, signals and journeys before cutover.
  • Connect JSON-LD to visible content, separate vocabulary validity from Google support and review templates and exceptions after changes.
  • Compare HTTP responses, rendering and interactions to find information missing during crawling.
  • Separate crawling, indexing, previews and AI service usage before changing site directives.
  • Coordinate URLs, links and incremental loading so items deeper in a collection remain discoverable.
  • Connect server responses, visible content and indexing decisions.
  • Change domain or URL structure while preserving useful destinations for old pages and their language editions.
  • Check the file offered to crawlers beyond simple XML syntax validity.
Useful questions
  • Does this page answer a distinct question?
  • Do language versions truly correspond?
  • Which source supports an important claim?
  • Do sitemap, links and canonical identify the same useful URL?
  • Does every old URL have a decision?
  • Does error-free validation guarantee a rich result?
  • Does Google execute JavaScript?
  • Can one file control all AI visibility?
  • Should the whole series canonicalize to page one?
  • Can an error page return 200?
  • Can every page redirect to the homepage?
  • Does a sitemap guarantee indexing?

Illustrative decision example

Situation
Fictional example: these inputs describe no customer or observed result. The displayed price changes, but a JSON-LD object built by another module retains the old value.
Check
Check a published page and its variants against visible price and the authorised business source.
Act
Restore consistency and check future data changes. Valid JSON does not establish that its values are true.

Structured data: distinguish valid JSON-LD from rich results

Structured data: verify meaning, evidence and supported features

Google Search Central — General structured data guidelines

Align content and representation

Align copy, visuals, alternatives and structured data. A complex image needs a text equivalent; valid markup or a tool-facing file does not guarantee search appearance.

Does essential information remain readable without images and verifiable at its source?

Explore the methods

Read data · verify · decide

Calculate overall CTR from clicks and impressions in the same scope. Brand queries and other intentions need separate interpretation.

Brand CTR
20%40 / 200
Other-query CTR
2.5%20 / 800
Combined CTR
6%60 / 1,000

Fictional teaching case — figures describe neither CIE nor a client.

Questions to support your decisions

Find answers and practical checks in the analyses in this category.

Explore the archive

Further analysis in this topic beyond the recent articles listed below.

References: data, uses and limitations

Documentation reviewed on .

References: data, uses and limitations
Source and purposeVerified data or benchmarkHow to use itLimitation to retain
Google · AI features and your website

Understand inclusion in Google Search AI features.

Google states that AI Overviews and AI Mode add no special technical requirements beyond applicable Search fundamentals. Check page access, indexability, snippet eligibility, links and useful textual content. Measure observed appearance, clicks and business outcomes separately.

Explore the method →

Eligibility guarantees neither crawling, indexing nor display. This documentation concerns Google Search, not every AI assistant.
Google · Structured data

Describe page contents through machine-readable markup.

Structured data helps search engines understand content. Marked properties should correspond to information actually present on the page. Choose a type matching the page and verify names, dates, relationships and sources. Check final rendering rather than only the template.

Explore the method →

Valid markup alone does not guarantee a rich result. It replaces neither the content nor feature-specific eligibility conditions.

Robots.txt: crawling, indexing and evidence

Separate crawl rules, index decisions and user outcomes

An SEO review becomes actionable when every conclusion points to an observed signal and its scope.

  • Name the rule and group explaining a crawl refusal or permission.
  • Treat canonical, noindex and sitemap as distinct mechanisms.
  • Add the effective Search AI control and keep conversions separate from impressions.

Review the twelve robots.txt cases →

References reviewed

IANA references and DNSSEC interpretation

Successful resolution enables access, not indexing

DNS enables reaching a destination; DNSSEC validation concerns DNS data authenticity. Neither guarantees crawling, indexing or ranking.

  • Separate DNS observations from HTTP status and indexing directives.
  • Do not infer a crawler’s recovery time from TTL alone.
  • Keep changes and checks by layer to explain what was actually restored.

Read the registries and try the cache model →

IETF · RFC 4033 · §3–5 · 2026-10-23

Reference material

Primary guidance published by the organizations responsible for these methods and standards.