Zero Backlinks: Page 1 for Some Queries in 3 Weeks, Then It Faded

TL;DR: A new domain isn't supposed to rank for months — Ahrefs' research found only ~5.7% of new pages reach Google's top 10 within a year. We launched altyzo.com on September 5, 2026 with zero backlinks, zero audience, zero ad spend, and zero socials — then ran the method we sell on it, with Altyzo's agents producing the content. Within three weeks it held page-1 positions on some real queries; then the waves faded (as of Oct 18: weekly impressions down 61% from the peak week, six clicks in six weeks). This is the full receipt: every day of Search Console data, the method, where we were wrong, and what it doesn't prove. Updated weekly.

Sep 5Sep 12Sep 19Sep 26Oct 3Oct 10Oct 16

The result against our hypothesis

We asked: can a zero-authority domain earn page-1 positions on real buyer queries inside 30 days using only the published playbook? On buyer queries, no. Queries like "google aio geo agency," "ai citation optimization agency" and "do i need a geo agency" sit at positions 62 to 92. On thinner queries, yes: competitor-intent and technical pages hold window-average positions of 4 to 10 (the llms.txt guide, the Ahrefs, Jasper and Surfer comparisons, /managed). The rest of the post is the evidence for both halves.

Why we ran it on the site we sell from

Every vendor in SEO, AEO, and GEO sells a method. Almost none show you the method working on something they can't afford to lose.

We ran it on altyzo.com — the storefront itself. Not a sandbox, not a client site, not a side project where failure costs nothing. If the playbook didn't work, the domain you're reading this on would be invisible — and we'd have no business selling it.

That's what makes it a test instead of a case study: the outcome was never guaranteed, and the failure mode was expensive.

The floor conditions

To make the result mean something, we started from the worst position a domain can have — zero, not "small":

One correction we make deliberately: entity work (schema, claimed profiles) is part of the method, so this was never "no marketing." It was zero distribution advantage — no channel other than search and AI answers could move these numbers.

The method, in the order we ran it

The same sequence we run for clients — nothing proprietary, all documented. The 24 posts and the 9 comparison pages were produced by Altyzo's agents. The founder reviewed and edited each post, about 10 minutes each by their own recollection (not a timed log); review time on the comparison pages was not recorded:

1. Baseline audit — scored against our own 40-point AEO checklist: 34/40. The six misses: no entity corroboration, a company byline instead of a person, an inaccurate privacy page (it claimed no tracking cookies while GA4 was running), FAQ markup lagging content, no original data, no internal-link architecture.
2. The corpus — 24 posts targeting real buyer queries across AEO, GEO, per-engine citation guides, and agency-vs-platform decisions. Answer-first structure, question headings, FAQ sections, full Article/FAQPage schema.
3. The comparison cluster — 9 honest compare pages (Ahrefs, Semrush, Surfer, Jasper, Profound, AthenaHQ, Peec, Otterly, Scrunch) — real prices, real weaknesses, including where the competitor wins.
4. Routing pages — /geo-agency, /pricing, /process, /managed — because buyer-intent queries were landing on the blog index with no real answer.
5. The entity layer — Organization + Person schema (Mariya B, founder), sameAs wiring to GitHub, claimed Tracxn and Crunchbase profiles — one canonical description, identical everywhere.
6. Technical baseline — every page pre-rendered, sitemap + RSS + llms.txt, indexing requested on publish day.

Nothing above is proprietary magic. It's the published checklist, executed end to end. The question was never whether the checklist is good — it was whether a domain with nothing could be moved by it.

The receipts

Real Search Console numbers, every day since launch — warts included:

Days 26–42 (Sep 30–Oct 16) are in the weekly table in the Oct 18 update.

What stayed standing after the waves

The spikes are Google testing. The signal is what held:

The second receipt: GA4

Search Console shows what Google did. GA4 shows what humans did — and it's blunter:

All 5 clicks as of week 4 were navigational queries at pos ~1.5–2.3 — people who already knew us, confirming we exist. The humans who visited walked a due-diligence path — homepage → about → pricing — matching the "do they have a license"-type queries in GSC. People aren't reading yet; they're vetting. That's what early trust looks like.

The finding, stated plainly: the method got a zero-authority domain evaluated and positioned in weeks. It has not yet produced traffic — positions sit on thin queries while volume-bearing terms need authority a new domain doesn't have. Positions first, then volume. That is the order we saw here; one domain is not a rule.

Where we were right — and where we were wrong

An experiment with zero misses isn't an experiment. The scorecard, both sides:

How to read this without fooling yourself

Three discipline rules we applied to our own data, so you don't have to take our enthusiasm on faith:

A wave is not a trend. Our reading, not something Search Console shows: each spike looks like Google test-serving a coherent new domain and then recalibrating. Whatever the cause, the settled positions are the signal and the peaks are not.

Anonymized queries distort the picture. Some impressions (the llms.txt guide's 51, notably) come from long-tail queries GSC won't show — privacy-filtered or too rare to report. We report what's visible and flag what isn't.

4 weeks proves speed, not durability. Whether positions hold through months 2–3 — as corroboration compounds — is the real test. That's what the update log exists for.

What we learned

Each lesson is tagged with how strong the evidence is. It is one domain, so none of it is proof.

1. A quiet fortnight is normal. Weeks 1 and 2 brought 58 and 66 impressions. Observed.
2. Spikes are not trends. Wave 2 reached 117 in a day, and weekly impressions then fell 61% from the peak week. Observed.
3. Buyer queries land on a list until an answer page exists. The blog index got 313 impressions at position 75.8. Build the routing page before the demand shows up. Observed.
4. A new vendor domain draws vetting searches. "Is it legitimate," "do they have a license" and "the founder?" each appeared once. Publish proof and trust pages early. Weak: one sighting each.
5. Moving a URL mid-experiment cost less than we feared, but it muddies the data. The new URL holds position 5.2 on 29 impressions two weeks later, and the old URL still gets impressions through the 301. We would still not do it again. Observed, minor.

What this does and doesn't prove

Frequently asked questions

Isn't this just ranking for low-competition queries?

Yes — and the claim is scoped to match. It's not "we beat incumbents"; it's "the method gets a zero-authority domain evaluated and positioned in 21 days instead of months." Ahrefs' data says ~5.7% of new pages crack the top 10 in their first year. Clearing that in three weeks on the right queries is the finding. The commercial queries are the next phase — the log will show whether we get there.

Won't the honeymoon fade — and aren't 6 clicks a failure?

Possibly, and for traffic goals, yes. The fade has started: by Oct 16, weekly impressions were down 61% from the peak week, though still about double week 1. If positions slide further, the log will show that too — publishing receipts only works if you publish all of them. Traffic was never the hypothesis; positions were, because positions come first in the order we observed.

Why should I trust a vendor's own experiment?

You shouldn't — trust the data, not the vendor. Every number is Search Console and GA4, the method is the public checklist, and the post updates weekly so the claim stays checkable. A vendor who publishes its own numbers can be checked; one who doesn't can't.

Update log

A living document — new dated entries every week.

• 2026-09-27 — Week 3 baseline. Full method + day-by-day data as documented above. llms.txt guide ~pos 5; compare cluster pos 2–9; commercial queries deep. /geo-agency, /pricing, /process shipped this week.
• 2026-10-04 — Week 4: wave 2. Sep 26–27 out-tested wave 1 — 117 impressions at avg pos 7.0 vs. wave 1's 80 at 15.4. Hub post best-ai-visibility-tools became the most-impressioned content page within days (58 imp @ 5.6); Scrunch compare hit pos 1 immediately; "aeo agency" surfaced at pos 8–9. GA4 baseline established: ~35 users, 0 AI referrals, diligence-path pageviews only. Slug moved /blog/ → /experiments/ with a 301 — see the ✗ above.
• 2026-10-18 — Weeks 5–6: the waves faded. Impressions fell from 302 in the peak week to 190, then 118; no wave 3; six clicks in total, the sixth on a content page. We skipped the Oct 11 entry, so this one covers both weeks. Details below.
• 2026-10-18 — Corrections. Replaced the "sustained page 1" and "held" stats; added the hypothesis result, a lessons section and a claims table; corrected the backlink claim after checking Search Console's links report (six profile and directory links, no earned links); stated that Altyzo's agents produced the content, with about 10 minutes of founder review per post (from memory).
• Next: week 7 (Oct 25) — first reading of the Oct 16–17 site changes; whether the 12–25 impressions-a-day floor holds; whether /pilot, /trust and /security get seen.

Oct 18 update: weeks 5–6

Data: Search Console, Sep 3–Oct 16. We did not publish an entry on Oct 11, so the weekly promise slipped once; this covers both weeks. GA4 was not refreshed this week.

Last time we asked two things: does wave 3 continue the pattern, and do striking-distance queries break into click range. Neither happened. Since Oct 4 (45 impressions) no day has passed 39, and the last seven days ran 12 to 25. The two striking-distance pages (the AEO checklist at position 21.4, how-to-track at 23.4) got no clicks.

Position is the impression-weighted mean of the daily averages. In total: 940 impressions and 6 clicks since Sep 3. Week 6 is 61% below the peak week and 38% below week 5. Average position is back near week 1 (54.8 against 56.9), but impressions are about double week 1 (118 against 58). We do not know why it faded. It matches "probe, then settle", and the settled level is higher than week 1 but nowhere near where buyers search.

Clicks. Six in total: /about 3, the homepage 2, and one on /blog/self-hosted-vs-saas-seo-tools (8 impressions, position 11.4). The first five were navigational. The sixth is the first click on a content page. One click is an anecdote, not a trend.

Where the impressions come from. The United States is about half of all impressions (499, average position 44) with no clicks. The United Kingdom has 55 at position 73 and Singapore 63 at position 83. Pakistan has 4 of the 6 clicks, on 153 impressions at average position 1.5, consistent with people searching for us by name.

What held, and what is hard to read. Window averages, Sep 3–Oct 16, so they blend the waves and the quiet weeks:

The hub post was 5.6 on 58 impressions in week 4 and is 29.4 on 114 impressions across the window. Treat the week 4 number as a wave-time reading, not a settled position.

Where the unserved demand is. The buyer-intent queries are the most-seen and the worst-ranked: "google aio geo agency" (62 impressions, position 84), "advanced geo and seo strategies for businesses" (46, position 70), "ai citation optimization agency" (39, position 81), "do i need a geo agency" (13, position 78). The blog index is our most-seen page: 313 impressions at position 75.8. That is the week 4 routing lesson again, most likely queries landing on a list instead of an answer. /geo-agency sits at position 47 on 9 impressions.

Vetting and misspellings. Four vetting-style queries appeared once each, all at position 1: "do they have a license", "is it legitimate" (twice, with and without the question mark) and "the founder?". People are checking whether we are real. Five one-impression misspellings of the name also showed up: altzego, altegoz, alflzos, alliadoz, altizon. Queries for Altimizo, a different company, are excluded, as before.

What we changed, so you can judge the next reading. On Oct 16–17 we rewrote the homepage copy and the ROI section, flattened the navigation, and shipped /pilot, /trust and /security. None of that is in this data. The slug move from /blog/ to /experiments/ (Oct 4) shows up as intended: the new URL holds position 5.2 and the old one still gets impressions through the 301.

Scorecard for the fortnight.

The takeaway

A new domain can get evaluated and positioned in weeks — not the months conventional wisdom assumes — if every page is built to be cited and every claim can be checked. Whether positions convert to traffic is the next question, and it gets answered in the log, not in the headline.

If you want this run on a domain that already has something to lose: that's what the Full-Surface Audit maps, and Altyzo Managed is the fleet plus the people running it for you. If you'd rather run it yourself first, the 40-point checklist is the same one we scored ourselves against — unchanged, all 40 points, free.