Move the definition into the first 60 words of the warehouse-native post

DrafteddraftExecutes now · produces a reviewable artefactprompt-executorheading restructure · impact 91 · effort M · updated 3h ago

The change

This executor renders a prompt rather than a patch — it does not touch your repo at all.

Self-contained: the issue, the change, file patterns for App Router, Pages Router and static layouts, and the acceptance checks restated as things to verify. Paste it into any coding agent.

Restructure the opening of https://acme.com/blog/warehouse-native-analytics
so the definition comes first.

WHY
Answer engines quote the first substantive claim on a page. On this page the
definition of "warehouse-native" is at word 340, behind three paragraphs of
scene-setting. For the tracked prompt "What is share of answer and how do I
measure it?" and its neighbours, engines quoted a competitor's definition on 4 of
6 runs — their version sits at word 12.

WHAT TO DO
1. Find the post body (MDX in content/blog/, or the page component that renders
   it).
2. Replace the opening paragraph — the one beginning "Every data team eventually
   hits the same wall" — with a two-sentence definition:

     Warehouse-native analytics means the product queries events where they
     already live — in Snowflake or BigQuery — instead of ingesting a second
     copy. One store, one bill, no reconciliation.

3. Keep the original opening. Move it down, under a heading like "Why teams end
   up here" — it is good writing, it is just in the wrong position.
4. Do not touch the rest of the post.

VERIFY
- The first 60 words of the rendered article contain "Warehouse-native analytics
  means".
- The original narrative opening still exists somewhere in the body.
- No heading levels were skipped (h1 → h2, never h1 → h3).

Why this fix

The evidence behind the recommendation, and what it is expected to move.

Engines quote the first substantive claim on a page. Yours is currently at word 340; a competitor's definition is at word 12 of theirs, and it wins 4 of 6 runs on pr_008.

First definition at word 340
pr_008 — competitor definition quoted on 4 of 6 engines

Source issue iss_003

Acceptance checks

How any of the three executors proves it worked. Identical for all of them.

first_words_containWarehouse-native analytics means
audit_issue_resolvediss_003

Verification

Re-measured at T+3d and T+14d against position.

2.9

baseline captured · after-value pending

7d before / T+14d after

Task

Task id: ft_03
Kind: heading_restructure
Executor: prompt-executor
Band: draft
Target: acme.com/blog/warehouse-native-analytics
Anchor: after_h1
Repo: not used
Requested by: Nightly run (scheduler)
Channel: REST
Created: 12 Aug 03:00 UTC

File targets

How the executor finds this page in a repo it has never seen.

App Router

app/blog/[slug]/page.tsx
content/blog/*.mdx

Pages Router

pages/blog/[slug].tsx

Static

blog/warehouse-native-analytics.html

Restructure the opening of https://acme.com/blog/warehouse-native-analytics so the definition comes first. WHY Answer engines quote the first substantive claim on a page. On this page the definition of "warehouse-native" is at word 340, behind three paragraphs of scene-setting. For the tracked prompt "What is share of answer and how do I measure it?" and its neighbours, engines quoted a competitor's definition on 4 of 6 runs — their version sits at word 12. WHAT TO DO 1. Find the post body (MDX in content/blog/, or the page component that renders it). 2. Replace the opening paragraph — the one beginning "Every data team eventually hits the same wall" — with a two-sentence definition: Warehouse-native analytics means the product queries events where they already live — in Snowflake or BigQuery — instead of ingesting a second copy. One store, one bill, no reconciliation. 3. Keep the original opening. Move it down, under a heading like "Why teams end up here" — it is good writing, it is just in the wrong position. 4. Do not touch the rest of the post. VERIFY - The first 60 words of the rendered article contain "Warehouse-native analytics means". - The original narrative opening still exists somewhere in the body. - No heading levels were skipped (h1 → h2, never h1 → h3).