Cap publishing on a new site at 3-4 URLs per week

Why this matters

Ten pages a day on a fresh domain reads as scaled content abuse. Start at three or four a week.

Before you start

• A new domain or a site without an established record of indexed, clicked pages
• Access to the CMS or publishing workflow and its scheduling settings
• Google Search Console verified for the site

How to apply it

1. Set a weekly ceiling of three or four URLs

   In the CMS or editorial calendar, schedule at most three or four new URLs per week for the first months of a new domain. Queue the rest as drafts rather than publishing them at once.

   Check: The sitemap or CMS published list shows no more than 4 URLs with a publication date in the last 7 days.

2. Apply a one-reader quality gate to every page

   Before publishing, confirm the page contains something a person would actually read: original examples, data or explanations rather than recombined text. Hold back any URL that fails the test.

   Check: The editorial tracker records reviewer sign-off for each of this week's URLs, and each has at least one section that does not restate an existing page.

3. Hold the throttle until Google sends clicks unprompted

   Do not raise the cadence while the site depends on promotion to get visits. Wait until Search Console shows organic clicks arriving on published pages without new distribution pushes.

   Check: The Search Console Performance report shows organic clicks in the last 28 days on URLs published before that period.

4. Open the throttle gradually once the click signal exists

   Increase output in small increments rather than jumping to a much higher daily rate, keeping the same originality gate on every new URL.

   Check: The new weekly URL count is higher than the previous week's, and the Pages report shows the newly published URLs indexed rather than accumulating as Crawled - currently not indexed.

<goal>
cluster breadcrumb route query index snippet snippet measure priority effort layout heading anchor metadata.
</goal>

<context>
pipeline metadata markup effort render audit heading render priority measure markup snippet query layout.
</context>

<discover_first>
metadata serp signal audit locale query payload breadcrumb locale alt section measure alt render.
</discover_first>

<constraints>
metadata serp section heading heading signal redirect layout priority query image page crawler redirect.
</constraints>

<plan>
sitemap section intent heading heading priority schema route serp content template priority verify canonical.
</plan>

<verify>
query audit snippet payload link image serp audit verify index route heading locale crawler.
</verify>

<report>
signal caching priority signal index link image index content canonical verify index report verify.
</report>

Source: @nicholasdulait on 2026-10-13 · original post · report an error