Google's Mueller: New Sites Need Time to Prove 'Unique Value'
Google's John Mueller says new sites need time to prove "unique value," advises quality over quantity, and tells owners to ignore failing GSC request indexing.

- John Mueller said Google's systems need time to understand a new site's 'unique value' before ranking it.
- The complaint cited 644 URLs in discovered sitemaps and failed Request Indexing attempts on November 1, 8 and 9.
- Mueller advised 'quality over quantity' content and focusing on normal crawling and indexing.
- Mueller said he would 'pass it on' regarding the GSC 'Oops! Something went wrong' errors.
- Google has discouraged using request indexing to force indexing in the past.
Google's John Mueller said on November 12-era Bluesky threads that Google Search needs time to understand a new website's "unique value" before ranking it properly. His advice to the site owner was blunt: prioritize quality over quantity and stop leaning on the Request Indexing button in Google Search Console.
What did Mueller actually say?
Mueller responded directly to a site owner on Bluesky whose new site was not being fully indexed. He wrote: "It's a fairly new site, and you've been busy with content — it can take time for the systems to understand the unique value of it all."
He then added a second recommendation: "So it's good to make sure it's really top notch (quality over quantity)."
Both statements are confirmed Google guidance, made publicly by Mueller on Bluesky. The message separates two things: indexing mechanics on one side, and Google's slower evaluation of what a new site actually offers on the other. The second process, per Mueller, cannot be forced from inside Search Console.
What was the site owner complaining about?
The original question was concrete. The site owner reported that "every 'Request indexing' in GSC fails with 'Oops! Something went wrong.'"
He supplied specific diagnostic details:
- The failure occurs even on the first attempt of the day, on November 1, 8 and 9.
- There is no "Quota exceeded" message.
- There are no manual actions on the property.
- Sitemaps were discovered fine, containing 644 URLs.
That is a substantial sitemap for a site the owner himself describes as fairly new. Mueller's answer reframed the problem: the failed manual requests were not the real bottleneck. Google's systems simply had not yet worked out what makes the site worth surfacing.
Is the Request Indexing tool the problem?
Mueller did not promise a fix for the error itself. He did say he would "pass it on" to the relevant teams, which confirms he treated the tool behavior as worth flagging internally. That is a confirmed escalation, not a confirmed bug.
His practical guidance went the other direction. He recommended "focusing on normal crawling and indexing" rather than worrying about the Google Search Console request indexing feature.
This is not a new position. Google has discouraged the use of request indexing as a way to force indexing in the past. Mueller's Bluesky reply extends that stance to the error case: even when the tool visibly fails, manual requests are not the lever that matters.
How much of this is confirmed versus speculation?
Confirmed, from Mueller's own words:
- New sites can take time for Google's systems to understand their unique value.
- Quality should take priority over quantity of content.
- He will pass the report about the failing requests on.
- Site owners should focus on normal crawling and indexing instead of the manual request tool.
Speculation, and labeled as such: the site owner's data points — 644 URLs, the November 1, 8 and 9 dates, the absence of quota errors — describe one property's experience, not a confirmed Google Search Console outage. Mueller neither confirmed a tool-side bug nor explained the "Oops! Something went wrong" error.
What should new site owners take from this?
The ranking implication is vertical-agnostic but size-dependent. Publishers launching with hundreds of URLs at once, like this 644-URL example, face the longest evaluation window under Mueller's framing. Sites with a smaller, higher-quality footprint give Google's systems less to assess and less to discount.
The operational takeaway is narrower. Request Indexing failures in Search Console, absent quota messages or manual actions, do not by themselves indicate a penalty or a technical crisis. Mueller's answer treats them as noise around the slower signal of Google learning what a site is for.
What to monitor next: whether Google acknowledges the "Oops! Something went wrong" errors after Mueller passes the report on, and whether Search Console documentation updates its guidance on manual indexing requests for new properties.
via bsky.app (Original)
More from Nathan Brooks
Show full bio
Senior reporter covering companies, deals and strategy in Search rankings and algorithm updates, generative engine optimization at SERP Journal.
211 articles