A website publishes stories in twelve languages. Traditional Chinese, English and Korean start gaining visitors. Other languages are quieter. Even simplified Chinese unexpectedly gets a few visits.
“But millions of people speak Spanish and use X. Why aren't those pages taking off?”
Because potential readers existing somewhere is different from a page being found in Google Search.[1] The shop may be open and the shelves may be full, but not everybody knows where the entrance is.
The automated topic finder already looks abroad
A publishing system can already be set up to find small games, memes and other topics with early reactions on X and video platforms, then make articles in twelve languages. That isn't a brand-new idea waiting to be invented.
But a rule existing isn't proof of how many Spanish, French or German topics were actually found and selected. Also, questions vary by region. Japanese readers may search “how to win”; overseas readers may first ask “what is this?” or “when can I play it here?”
Twelve languages create twelve possible doorways, not twelve guaranteed lines of customers. Translation finishes the publishing job, not the discovery job.
Googlebot has old errands as well as new deliveries
An anonymized operating case dated October 23, 2026 had roughly 29,000 article URLs. It added 5,431 new URLs over seven days. Google fetched around 1,500 to 2,200 article URLs per day.
That daily number exceeds the average daily supply of new URLs. Why the delay? Because Google also checks older articles, looks for updates, and follows other paths through the website. New pages don't get a dedicated express checkout.
The same case recorded temporary server errors, missing pages and sitemap trouble. Imagine a delivery inspector arriving at a shop and occasionally finding the shutters down. Server speed and reliability can affect how much Google fetches.[1][2]
And “indexing not confirmed” isn't the same as “Google read it and rejected it.” Some pages haven't been discovered at all.
Unchanged article? A shorter answer works
When Google checks whether a previously visited page has changed, the server can respond with 304, meaning “not modified,” if the content really is the same. There is no need to send the entire article again.[3]
It's like checking a book's edition number instead of rereading every chapter. The server saves time and data.
But the versions must be compared correctly. A changed article must return the changed content, and Google doesn't send a conditional request every time. A 304 isn't a secret “crawl my new articles first” ticket. It just makes repeat visits cheaper.
Put signs where Google can actually see them
Only change sitemap modification dates when the relevant content genuinely changes. Calling every old item “NEW!” each morning makes the label meaningless.[4]
Keep clear, compact lists of recent pages for each language and register sitemap locations in Google's tools when appropriate. Don't resubmit the exact same unchanged sitemap after every single article. Google explicitly advises against that.[5]
Link from the main homepage, language homepages and article lists to new pages. Clean up pointless URL variants, redirect chains and broken pages. Five fake entrances to the same storage room don't make five useful stores.
No search appearance after 28 days: delete it?
Not automatically. Google may not have discovered the URL, fetched it, indexed it, or ranked it high enough. The title may also fail to match the words local readers actually search for.
Check discovery, fetching, indexing and impressions separately. Then consider updating, combining similar pages or proposing exclusion from search. Zero impressions aren't permission to delete an article.
An hourly report could split Google's daily article fetches into pages published within seven days and older pages, separating full fetches, 304 replies and server errors. That would show whether new content is receiving a greater share of visits.
The article factory is fast. Reception is overwhelmed.
Before slowing production, fix errors, make old-page revisits lighter and give new content clearer paths. No publisher can dictate Google's precise crawl order.
Twelve languages. Fresh stock every day. Global opening hours.
And the reception desk is still sorting yesterday's deliveries.
These figures describe one anonymized case, not a Google-wide average. The proposed fixes are not claims of completed deployment or proven traffic gains.
References (5)
- Google, Crawl budget developers.google.com
- Google, HTTP status codes developers.google.com
- Google, HTTP caching and 304 developers.google.com
- Google, Sitemap lastmod developers.google.com
- Google, Avoid unchanged sitemap resubmissions developers.google.com
