Original research - 4 July 2026
Search Demand Action Map 2026
Audit-ready action map for turning local GSC, SERP and AI answer-surface evidence into content, page and technical SEO/GEO changes without publishing private query data.
This is the public decision workflow for acting on private search demand. It defines how local query, SERP and AI evidence becomes title, answer-capsule, internal-link, source-depth, no-create, freshness or outcome-publication work without exposing private exports.
7
Action rules
4
Critical gates
20
Local commands
13
Experiments covered
15
No-create rules
Methodology and limits
Rows convert local Search Console opportunity types, competitor battlecards, SERP/AI snapshot protocols and technical SEO controls into auditable action rules.
Raw Search Console exports, query strings, clicks, impressions, CTR, positions, SERP screenshots, AI transcripts, export hashes and reviewer notes stay local unless reviewed, redacted and aggregated.
The map proves the decision workflow for acting on search demand; it does not prove that rankings, traffic, AI citations, backlinks or the 500k/month objective have been achieved.
- This is a public action map, not a dump of private Search Console or analytics rows.
- A local query opportunity does not justify a new indexable page unless source-backed uniqueness, crawl path and maintenance owner are proven.
- Passing this workflow does not guarantee rankings, traffic, AI citations, backlinks or market-share gains.
Action matrix
| Rule | Priority | Trigger | Commands | Public surfaces |
|---|---|---|---|---|
high-impression-low-ctr-snippet-refresh title-snippet-answer-refresh | critical | A local GSC opportunity row is high-impression-low-ctr, has a position-based CTR gap of at least 2 percentage points, and maps to an existing source-backed page. |
| |
striking-distance-internal-link-push internal-link-authority-push | critical | A local GSC opportunity row sits in positions 5-15, has material impressions, and the target page already has source-backed content that deserves more crawl and internal authority. |
| |
page-two-source-depth-section source-backed-depth-section | high | A local opportunity row is page-two, maps to a canonical page, and the current page lacks a source-backed section that answers the query fully. |
| |
emerging-demand-canonical-routing canonical-routing-no-create | high | A local opportunity row is emerging-demand, unmapped, or below the page-creation threshold, but the query reveals user language the existing site should route better. |
| |
serp-ai-market-share-escalation serp-ai-market-share-escalation | high | Reviewed local SERP or AI answer-surface snapshots show competitor source classes owning a battlecard query, or no Visa Atlas URL/citation appears where a target page should be visible. |
| |
freshness-stale-claim-refresh freshness-stale-claim-refresh | critical | A local query, AI answer, source update or fact-change row indicates users are asking for latest/current/2026 information where stale public figures would create YMYL risk. |
| |
experiment-outcome-publication-gate experiment-outcome-publication-gate | critical | A local title, snippet, answer-capsule, internal-link or AI-citation experiment has completed baseline and comparison windows and needs a ship, iterate, revert or monitor decision. |
|
Content, page and technical changes
- critical
high-impression-low-ctr-snippet-refresh
Raw queries, clicks, impressions, CTR, position rows, screenshots and comparison-window exports stay local unless reviewed and aggregated.
Content changes
- Rewrite the title, meta description and first visible answer so the snippet names the current figure, date and official source class.
- Tighten or add one source-backed answer capsule that directly answers the matching query.
- Keep stale-answer caveats visible when the query asks for latest, current, 2026 or changed figures.
Page changes
- Edit the existing canonical page rather than creating a new query page.
- Move the answer block above generic explanatory prose when the query is fact-led.
- Add a visible citation/reuse link to the source dataset when the answer uses a reusable figure.
Technical changes
- Verify the edited page keeps canonical, Article, Dataset/DataDownload and noindex controls intact.
- Update the public search index description only when the rendered page promise changed materially.
- Run rendered SEO after the build, not only source checks.
No-create rules
- Do not create a new page for a low-CTR query when an existing canonical page can answer it.
- Do not change title/meta to promise a figure that is not visible in the rendered first screen.
Pass criteria
- The rendered page contains the promised answer, source URL, review date and canonical URL.
- The matching battlecard experiment records title-snippet or answer-capsule as an allowed experiment type.
- The local comparison window is evaluated before any public outcome claim is made.
Failure response
- Revert or iterate the snippet if comparison-window CTR does not improve without position loss.
- Escalate to source-depth work if the page cannot answer the query without a new sourced section.
Source datasets
Local evidence inputs
- Search Console query/page export with declared period, redacted property label and search type.
- Local opportunity row from seo:gsc-opportunities with opportunityType=high-impression-low-ctr.
- Matching public battlecard experiment when the query or target page matches a battlecard rule.
- critical
striking-distance-internal-link-push
The reason a specific query/page is striking distance comes from local GSC rows and must not be published directly.
Content changes
- Do not rewrite the page from scratch; strengthen the exact query answer and nearby explanatory paragraph.
- Add one compact table, answer capsule or comparison callout only when it is source-backed.
Page changes
- Add descriptive internal links from the relevant hub, calculator, data page or research report.
- Use anchor text that matches the source-backed topic, not generic "learn more" anchors.
- Keep sibling links within the same topical cluster so crawl signals remain coherent.
Technical changes
- Confirm the internal-link target appears in static HTML, not only client-side state.
- Confirm sitemap and indexable-page manifest still include the target when it is meant to rank.
- Check rendered artifact size and noindex controls after adding links.
No-create rules
- Do not create a duplicate page to chase a position 5-15 query before internal links and answer clarity have been tested.
- Do not add sitewide footer links for one query cluster; use cluster-relevant links only.
Pass criteria
- At least two relevant crawl entry points link to the target with descriptive anchors.
- The target page retains visible source context and no accidental noindex.
- The comparison window is measured with the same GSC property label and search type.
Failure response
- Remove low-value links if they dilute unrelated clusters or fail rendered checks.
- Escalate to source-depth or authority distribution if internal links do not move the cohort after the comparison window.
Source datasets
Local evidence inputs
- Local opportunity row from seo:gsc-opportunities with opportunityType=striking-distance.
- Indexable page manifest row proving the target page is intended to be indexed.
- Topical authority cluster row identifying the correct hub, spokes and anchor patterns.
- high
page-two-source-depth-section
The exact query and page-two performance evidence remain local; public artifacts expose only the source-backed section and planning rule.
Content changes
- Add a focused source-backed section, table or decision block to the existing page.
- Reference the government source, public dataset and review date next to the new answer.
- If competitor pages win with unsupported prose, answer with a compact sourced comparison instead of longer generic copy.
Page changes
- Place the new section under the nearest existing heading unless the query deserves first-screen treatment.
- Add row-level anchors when the section contains reusable figures.
- Link back to the source dataset and related calculator or report.
Technical changes
- Keep Article/Dataset JSON-LD consistent with the new section and source datasets.
- Update answer-capsule extraction if the section becomes a reusable short answer.
- Verify the page remains below thin-page and rendered artifact risk thresholds.
No-create rules
- Do not create a new page unless the section would exceed the scope of the existing canonical page and has at least two durable source-backed subtopics.
- Do not add unsourced prose just to increase word count.
Pass criteria
- The added section has at least one official source or public dataset link.
- The page still has a single canonical intent and does not duplicate a stronger existing page.
- The public battlecard or content opportunity row explains why this depth exists.
Failure response
- Remove or noindex content that cannot be source-backed.
- Merge duplicated sections back into the canonical page when the query does not justify a standalone asset.
Source datasets
Local evidence inputs
- Local opportunity row from seo:gsc-opportunities with opportunityType=page-two.
- Rendered page review showing the query answer is missing, buried or not source-backed.
- Competitor battlecard gap showing the source class or answer format to beat.
- high
emerging-demand-canonical-routing
Emerging query strings, one-off user language and Search Console rows remain local; public changes expose only canonical routing and source-backed content.
Content changes
- Map the query wording to the best existing canonical answer before any page creation.
- Add a small glossary, alias, FAQ-style answer or internal-link anchor only when it improves an existing source-backed page.
- Use public search-index keywords to make the canonical page easier for on-site and AI retrieval.
Page changes
- Prefer editing hubs, calculators, data pages or reports that already own the intent.
- If no canonical page exists, record the missing source-backed asset in the content opportunity map before building.
Technical changes
- Update search-index metadata and topical authority links when canonical routing changes.
- Keep non-qualified long-tail combinations excluded from sitemap and guarded from indexing.
- Run noindex and thin audits after any routing or page-class change.
No-create rules
- Do not create a page from one emerging query row.
- Do not index a page class unless it has unique sourced data, a crawl path and an expected maintenance owner.
- Do not use machine-translated or runtime-generated text to cover query variants.
Pass criteria
- Every emerging query is routed to an existing canonical page or deferred with a documented source-data requirement.
- No new URL enters the sitemap without passing source, thin and noindex gates.
- The public search index points users and AI retrievers at the canonical target.
Failure response
- Keep the query in the local backlog until enough source-backed demand exists.
- Remove any speculative page from sitemap and search index if it lacks unique source value.
Source datasets
Local evidence inputs
- Local opportunity row from seo:gsc-opportunities with opportunityType=emerging-demand.
- Search index and sitemap review showing whether a canonical target already exists.
- Noindex/thin-page audit results for any proposed new URL class.
- high
serp-ai-market-share-escalation
Raw SERP screenshots, AI transcripts, prompt outputs, browser profiles and unredacted competitor evidence stay local unless reviewed and aggregated.
Content changes
- Refresh the affected battlecard answer format against the observed competitor source class.
- Add missing source-backed answer capsules or citation-pack rows for the exact stale or unsupported AI answer gap.
- Prepare publisher citation kit updates when the issue is authority, not on-page answer quality.
Page changes
- Strengthen the target page or report that the answer engine should cite.
- Link the target page from the relevant research, data and AI-agent entry points.
Technical changes
- Confirm crawler access and rendered schema for the target before treating the gap as an authority problem.
- Log the snapshot cadence and competitor source class before changing the battlecard.
- Keep raw screenshots and transcripts out of public code and pages.
No-create rules
- Do not infer market-share loss from one unreviewed screenshot or one prompt.
- Do not publish competitor-win claims until the snapshot summary has reviewed aggregate evidence.
Pass criteria
- The affected battlecard links the query cluster to a target page, source dataset and measurement command.
- The target page passes rendered SEO and answer-capsule checks before authority outreach is blamed.
- Any public market-share claim is supported by an approved aggregate rollup.
Failure response
- Fix crawler/rendered/source issues before starting authority outreach.
- If the target is technically sound but invisible, escalate to publisher kits, repository mirrors or authority distribution.
Source datasets
- /api/public/visibility-metrics
- /api/public/competitor-query-battlecards
- /api/public/battlecard-search-experiments
- /api/public/content-opportunities
- /api/public/topical-authority-map
- /api/public/technical-seo-controls
- /api/public/seo-geo-audit-evidence
- /api/public/serp-answer-surface-snapshots
- /api/public/quarterly-market-share-summary
- /api/public/publisher-citation-kits
- /api/public/authority-distribution-plan
Local evidence inputs
- Local SERP/AI snapshot JSONL summarised by seo:surface-snapshots.
- Reviewed market-share summary generated by seo:market-share-summary when approved for publication.
- Public competitor query battlecard for the affected query cluster.
- critical
freshness-stale-claim-refresh
Source-refresh notes, failed live probes, AI answer transcripts and private query evidence stay local unless reviewed and aggregated.
Content changes
- Update the affected figure, answer capsule, citation pack and visible change note from the official source.
- Add a stale-answer caveat when model consensus or competitor pages are likely to lag the current government source.
- Link the exact fact-change row when an old value changed to a new value.
Page changes
- Refresh the canonical page first, then downstream summaries, calculators and research pages.
- Keep review dates visible near the changed answer, not only in JSON.
Technical changes
- Run source and freshness audits before publishing a changed high-risk figure.
- Run liveness when the change is a source-refresh or release-signoff event.
- Verify Dataset/DataDownload, Claim boundaries and rendered answer capsules after the update.
No-create rules
- Do not publish a latest/current page unless the maintenance SLA and source owner are explicit.
- Do not quote a figure from AI output, competitor prose or a cached snippet without official source verification.
Pass criteria
- The changed value, old value when known, source URL and review date are visible or available through a public feed.
- No stale high-risk record remains in freshness output before release sign-off.
- The affected answer capsule or citation pack matches the canonical source-backed page.
Failure response
- Freeze the affected page or section until the source can be verified.
- Remove stale snippet promises from title/meta and answer blocks if the fact cannot be refreshed.
Source datasets
- /api/public/visibility-metrics
- /api/public/competitor-query-battlecards
- /api/public/battlecard-search-experiments
- /api/public/content-opportunities
- /api/public/topical-authority-map
- /api/public/technical-seo-controls
- /api/public/seo-geo-audit-evidence
- /api/public/freshness
- /api/public/fact-changes
- /api/public/ai-answer-accuracy-audit
Local evidence inputs
- Local GSC opportunity row containing latest/current/year terms or an AI answer accuracy miss.
- Freshness report or fact-change row for the affected figure or route.
- Source verification notes when liveness is run before publication.
- critical
experiment-outcome-publication-gate
Raw GSC exports, query rows, export hashes, screenshots, reviewer notes and failed experiment details stay local unless reviewed and aggregated.
Content changes
- Ship, iterate, revert or monitor the exact changed element; do not generalise one result across unrelated clusters.
- Record whether the winning move was title/snippet, answer capsule, internal links, source depth or AI-citation support.
Page changes
- If shipped, preserve the changed page and related internal links through rendered audits.
- If reverted, restore the previous source-backed answer and keep the failed experiment out of public claims.
Technical changes
- Reject outcome rows without matching experiment ID, baseline/comparison scope, redacted export hash and reviewer fields.
- Keep private evidence out of public reports unless converted into approved aggregate rows.
No-create rules
- Do not call an experiment successful from impressions alone.
- Do not publish a ranking, traffic or market-share claim from a failed or unreviewed local outcome row.
Pass criteria
- The outcome row references a public experiment ID and matching target pages.
- Baseline and comparison periods do not overlap and use the same property label and search type.
- Public claims, if any, are aggregate and approved for publication.
Failure response
- Keep the goal active and the outcome private until the evidence is complete.
- Rebase the content opportunity priority score if repeated experiments underperform.
Source datasets
Local evidence inputs
- Approved local GSC experiment outcome JSONL with baseline and comparison windows.
- Matching public battlecard experiment ID and target pages.
- Rendered audit output after any shipped change.
Cite or reuse this dataset
This search demand action map is free to reuse under CC BY 4.0. Cite the JSON endpoint for machine-readable action rules and the report page for methodology and private-data limits.
Suggested citation
Visa Atlas, "Visa Atlas search demand action map", https://visaatlas.org/research/search-demand-action-map-2026. Last verified 4 July 2026.
Primary sources (17)
- /api/public/visibility-metrics
- /api/public/competitor-query-battlecards
- /api/public/battlecard-search-experiments
- /api/public/content-opportunities
- /api/public/topical-authority-map
- /api/public/technical-seo-controls
- /api/public/seo-geo-audit-evidence
- /api/public/search-index
- /api/public/indexable-pages
- /api/public/answer-capsules
- /api/public/freshness
- /api/public/fact-changes
- /api/public/ai-answer-accuracy-audit
- /api/public/serp-answer-surface-snapshots
- /api/public/quarterly-market-share-summary
- /api/public/publisher-citation-kits
- /api/public/authority-distribution-plan