Layered cake SEO is the practice of building one specialist microsite for every service in every suburb around a main business site, so each page targets a single search intent. SEO practitioner Jesse Cunningham laid out the method in an August 2026 video: an anchor site with the reviews, a grid of cheap specialist sites around it, tracked numbers on every layer, and strict rules to avoid a shared Google footprint.
What is layered cake SEO?
Layered cake SEO is a strategy of building many small specialist websites around one main business site so each one targets a single service in a single suburb. SEO practitioner Jesse Cunningham, who runs the Rank Expand academy and channel, coined the term in an August 2026 video to describe how he stacks service-by-town microsites into a grid that outranks generalist competitors on Google.
The name sounds odd, but the logic is plain. One roofing website fights for metal roofing, roof replacement, storm damage, and every nearby town at the same time. Cunningham argues that a site dedicated to one of those sub-niches presents a clearer, more complete answer, which matters more now that Google surfaces AI Overviews and evaluates which page best satisfies the query.
The anchor site still matters. It carries the Google Business Profile, the accumulated reviews, and the brand. The microsites sit around it as specialist layers, each covering one service in one geography.
Why specialist sites beat generalist sites on Google
Google increasingly rewards the page that matches the searcher's exact intent, and searchers type sub-niche phrases, not broad category words. A query like "Kansas City metal roofer" describes a specific need; a generalist roofing homepage dilutes that signal across every service it offers.
Cunningham illustrates the point with the search results themselves. He compares a specialist result like Stonescape Steel Roofing and Exteriors, showing a small review count, against generalist roofing sites with 200 to 400+ Google reviews that dominate broader terms like "Kansas City roofer." His claim, drawn from his own campaigns rather than an independent study, is that specialist sites win the sub-niche queries even with fewer reviews.
Two pressures reinforce this. First, AI-generated websites have multiplied the supply of competing pages. Second, Google's map pack is shrinking as AI Overviews absorb more of the results page, which reduces calls and visits for businesses relying on a single listing. Cunningham's response is to stop depending on one listing and spread across many.
How the microsite grid works
The grid multiplies service layers by towns. Cunningham's worked example: a roofing company with six sub-niches across a metro like Kansas City builds a dedicated site for each service in each suburb. A 4-by-5 arrangement of suburb rows and service columns is 20 websites; a 4-by-3 arrangement is 12. Each box in the grid is a separate microsite with its own domain.
Not every site in the grid performs. Cunningham is explicit that some crush and some do not, and the losing sites get retired. The economics make that tolerable because build costs have collapsed: he puts the cost of a microsite at roughly 10 to 15 dollars, essentially the domain registration, with AI tools handling production.
Prioritization matters more than coverage. He advises going after the sub-niches with the highest revenue per lead first, such as metal roofing or roof replacement in the roofing example, rather than building the full grid blindly.
Site structure: what a microsite should contain
Each microsite must read as a genuine specialist site, and Cunningham specifies a size: 30 to 50 pages in his opinion. The structure matters because Google has to perceive the site as a focused authority for one service in one area, not a doorway page with a swapped town name.
His team uses a one-click website builder inside the academy that collects business services, towns, content, and photos, then outputs a structured file. That file is handed to an AI coding agent such as Claude Code, Anthropic agentic coding tool that runs in the terminal, or OpenAI's Codex to generate the site. Cunningham describes this as boxing up the structure so members replicate the same layout.
Quality bar, in his words: the site does not need to be beautiful. A five-out-of-ten design converts well in blue-collar niches, and his best performers are judged by call volume, not aesthetics. What the site cannot be is a thin clone or spun content; it has to satisfy a human visitor who lands on it.
Answering calls and monetizing the leads
Every microsite carries a unique tracked phone number, which costs about a dollar per number and lets Cunningham attribute each call to a specific layer of the grid. When a call comes in, an AI receptionist answers 24/7, qualifies the lead, and produces a transcription and synopsis.
That call data feeds two business models. Rank and rent: the operator sells the qualified leads to a local business. Owner-operator: the business runs the grid itself and keeps every lead, which Cunningham calls the way to make the most money.
He also notes an operational detail that affects rankings: unanswered calls hurt. In his experience, Google can observe when visitors call a number on a site and nobody picks up, and those sites fall.
Footprint risk: how to avoid a mass de-index
The biggest objection to this strategy is detection, and Cunningham has a concrete cautionary case. A friend running 300+ microsites had all of them de-indexed overnight about two years before the video because every site was verified under a single Google Search Console account. One shared account linked the whole network.
His operating rules, from the same account:
- No Google product tied to the microsites. No Google Search Console verification, no indexing requests through it, no Google Analytics.
- No thin clones. Six copies of one page with the town name swapped are treated as doorway spam; each site gets distinct content.
- No fake companies and no overnight builds. The stack is built one solid layer at a time.
- Real specialist content that a human is glad to land on, because Google observes satisfaction signals such as completed calls.
He does not claim the approach is undetectable, only that avoiding shared Google accounts and producing genuinely distinct specialist sites reduces the footprint that took down the 300-site network he describes.
Frequently asked questions
- What is layered cake SEO in one sentence? It is a strategy of building one specialist microsite per service per suburb around a main anchor website, so each site targets a single search intent instead of one generalist site fighting for all of them.
- How much does a microsite cost to build? Cunningham reports roughly 10 to 15 dollars per site, mostly the domain, because AI tools generate the pages. Tracked phone numbers add about a dollar each.
- How many pages should a microsite have? Cunningham's guideline is 30 to 50 pages, structured so the site reads as a genuine specialist for one service in one town.
- Is this strategy spam? Cunningham argues it is not, provided the sites are distinct specialist resources rather than doorway clones, and provided you avoid shared Google accounts, which he says caused a 300-site network to be de-indexed in a case he describes.
- Do I need a Google Business Profile for every microsite? No. The anchor site carries the main profile and reviews. Adding a profile to each microsite is an optional next level, but Cunningham says sites can earn well ranking below the map pack without one.
Turn a video like this into an article
Everything above came out of an 11-minute video, and that is the pattern worth noticing: working practitioners pack specific, repeatable methods into recordings that search engines barely surface. Cunningham's grid math, his cost figures, and his de-indexing story all lived inside a transcript before they lived on a page.
If you have videos like that, your own or ones you have rights to publish, Skala blog turns a YouTube URL into a structured written article: paste the link, transcribe the video, and generate a draft you can edit. For more tools and resources, see crazystack.com.br.
This piece was produced from the channel Dev Doido do canal do youtube's workflow reference and the Rank Expand source video, then verified and structured for search.
Fork this article
Start a new branch from the same video, shaped your way. You keep the credit; the original keeps the attribution.
A fork in another language is filed as a translation of this article, so the two pages point at each other. You can unlink it later from the editor.
0/240
You are creating
- Format
- For
- Language
- Source
- Your angle
You will be asked to sign in before it is generated.
Buy credits