Drip-feed indexing: scheduling URL submissions over days
Drip-feed changes when URLs are submitted for crawling, not how. It is the right tool when your list is large relative to the crawl attention your domain currently earns, and the wrong tool when you are simply in a hurry.
Every indexing campaign has two variables: the list of URLs and the rate at which you hand them over. Most people only think about the first one. Drip-feed is the discipline of treating the second one as a deliberate choice.
What drip-feed actually changes
A submission is a request for a crawler to visit a URL. Ten thousand requests sent on Monday and ten thousand requests spread across a fortnight contain identical information. What differs is the shape of the demand curve you create, and the shape of the growth curve an outside observer would infer from your link profile.
That second point is the one worth dwelling on. If a domain that has never had more than forty referring pages suddenly acquires eight hundred in a single day, the pattern itself is information. Nobody outside Google can tell you exactly how that information is weighted. What we can say from our own campaign data is that customers who ration submissions report fewer stalled batches than customers who dump everything at once — and that is a correlation from our own book of work, not a law of the search engine.
When a spread schedule is the right call
- Your list is large relative to your domain's history. A three-month-old site submitting six hundred URLs is a different proposition from a five-year-old site doing the same thing.
- The links are mixed in quality. Directories, profiles and comment placements bought in bulk look different arriving in a trickle than arriving as a wall.
- You have no deadline. Drip-feed costs you time. If nothing depends on the links being live this week, time is the cheapest currency you have.
- You want a readable signal. A spread schedule lets you watch the indexation rate move day by day. A single dump gives you one data point and no diagnosis.
When it is the wrong tool
Drip-feed is not a quality filter. Spreading bad links over three weeks produces the same bad links, just later. It also does not help with a page Google has already crawled and declined to index — that is a content decision, not a scheduling one, and it is covered in crawled – currently not indexed.
And if you have a launch, a seasonal window or a client report due Friday, a spread schedule is actively working against you. Use the standard mode and accept the risk consciously.
Sizing the daily volume
There is no published safe number, and anyone quoting one is guessing. The workable method is relative: anchor the daily figure to the crawl attention your domain already earns, which you can read from the Crawl Stats report in Search Console. That method is worked through in how many URLs per day should you submit.
What to measure
Three numbers tell you whether the schedule is doing anything: the share of each day's batch that ends up indexed, the lag between submission and first crawl, and the share that quietly falls back out of the index a month later. The third is the one almost nobody tracks, and it is the reason link decay exists as a separate topic.
Guides in this section
Questions
Does drip-feed guarantee indexation?
No. Scheduling affects when a crawler is asked to visit, not whether Google decides the page is worth indexing. Pages that are thin, duplicated or poorly linked internally will be declined at any submission rate.
How long should a drip-feed schedule run?
Long enough that the daily volume sits within the crawl attention your domain already earns. For most campaigns that is between one and four weeks; the standard SpeedyIndex task window is seven days.
Schedule it instead of sending it
SpeedyIndex spreads your list across the days of a task, verifies each URL afterwards and charges only for the ones confirmed as indexed.
See the Drip-Feed page