# Google sandbox The Google sandbox is the idea that Google holds back new domains from ranking for months. Google has not confirmed a sandbox. It says new sites need time while systems gather signals. This entry shows how to tell normal ramp from a real issue, and what to do meanwhile. Updated 2026-09-14 · Source: https://porteur.ai/glossary/google-sandbox ## What founders observe You launch, submit the sitemap, and some pages get indexed. Branded queries show, but product queries do not. Impressions creep up, clicks do not. This pattern is common on competitive terms. A brand new yourproduct.com will rarely rank for “project management software” next week. It might for “yourproduct pricing” or a long query like “export kanban board to csv yourproduct” first. ## What Google says There is no confirmed sandbox mechanism. As of 2026, Google explains the lag by the time its systems take to understand a site and its signals. New sites start with little data. Core updates are broad changes to ranking systems. They roll out several times a year, and a rollout takes about two weeks. Drops around a core update are usually reassessments of content. There is “nothing to fix”, you improve quality, originality, usefulness and E-E-A-T, then often wait for a later update for recovery. Spam updates and manual actions are different. Spam updates, including SpamBrain, target policy violations like cloaking, doorway pages, link spam, scaled content abuse and thin affiliates. Manual actions are human reviews listed in Search Console. You fix, then file a reconsideration request and wait days to weeks for review. ## How to judge your case 1. **Check indexing and coverage** In Search Console, use URL Inspection on “/”, “/pricing”, and a deep page like “/guides/getting-started”. Confirm “Indexed” and that the indexed URL matches your canonical. 2. **Read the Performance report** Filter by the last 28 days. Compare branded queries to generic. A healthy ramp shows rising impressions on long queries before head terms. Save a query filter for “yourproduct” to separate brand. 3. **Scan for manual actions and security issues** Open Manual actions and Security issues. If present, read the type and affected pages. Fix before anything else. 4. **Check the timing against updates** Look at the Search Status Dashboard for core or spam updates across the date you saw a change. Set expectations: recovery may need a later update. 5. **Review crawl stats and internal links** In Crawl stats, confirm Googlebot visits your main sections. Add clear links from the homepage and “/guides” to the pages you need to rank. > Do not confuse a slow ramp with a penalty. If there is no manual action, treat it as signal building, not punishment. ## What to do while you wait - Ship pages that answer narrow intents first. Example: “/guides/import-from-trello” can rank before “project management software”. - Tighten on page. Clear titles under about 60 characters, specific H1s, unique meta descriptions, and helpful body copy with real examples and screenshots. - Earn and cite evidence. Publish case studies, docs, and product pages with specifics, not fluff. Show author names and how you tested claims. - Build internal links. From “/guides/getting-started” and “/pricing”, link to your core pages with descriptive anchor text. - Get a few real links. Reach out to partners and listings that actually use your product. Avoid schemes that buy or trade links at scale. - Watch Core Web Vitals. Keep LCP around 2.5 seconds, CLS around 0.1 and INP around 200 ms. Fix obvious layout shifts and slow images. - Track queries in Search Console. Group by topic. When a page starts getting impressions for a head term, expand it or add a supporting page. A fixed page looks like this: a crisp title, an intro that answers the query, product specifics, screenshots, and links to deeper pages. No filler or boilerplate across pages. ## Traps to avoid - Buying links or joining private blog networks. These are link spam and can trigger spam systems or a manual action. - Churned or scaled content. Hundreds of near-duplicate pages is scaled content abuse and will not speed up trust. - Doorway pages that funnel to one page. Build one strong page for a topic instead. - Submitting disavow files because a tool says “toxic”. Google says most sites do not need it, and the file is not easy to undo. - Blaming “negative SEO”. As of 2026, Google says its systems ignore bad links in nearly all cases. - Sneaky fixes during updates. There is nothing to fix for a core update drop beyond improving content and site experience. > Only use the disavow tool if you have a manual action for link spam or a history of paid links you cannot remove. ## Questions ### Is the Google sandbox real? It is a name for a pattern, not a confirmed system. New sites often take months to rank on competitive queries because Google has little signal at first. Google attributes the lag to signal gathering, not a sandbox switch. ### How long does a new site take to rank? There is no set time. You will usually see impressions rise first on long, specific queries. Head terms can take months on a fresh domain, especially in crowded markets. ### Could my site be penalised instead of sandboxed? Check Search Console. If you have a manual action or security issues, fix those. If not, and you follow spam policies, treat the slow ramp as normal signal building rather than a penalty. ### Should I build lots of pages to speed it up? Quality beats volume. Shipping many thin or near-duplicate pages risks scaled content abuse and doorway patterns. Publish focused, useful pages and connect them with internal links. ### Do I need to disavow toxic backlinks on a new site? Usually no. Google says it ignores most bad links and that disavow is for sites with a manual action for link spam or a past of paid links you cannot remove. ### Can a core update help or hurt a new site? Yes. Core updates reassess content across the web. If you improve quality and usefulness, a later update may lift you. If you drop, there is nothing to fix beyond improving content and waiting for the next update. ## Read next - [How to use Google Search Console in ten minutes a week](https://porteur.ai/guides/how-to-use-google-search-console): A quick weekly routine: set four filters, compare 28 days, check pages then queries, and fix three findings, without getting lost in noise. - [The Search Console performance report, column by column](https://porteur.ai/guides/search-console-performance-report): Every column in the Google Search Console performance report explained with the traps that trip small sites, and how to act on each. - [A Google core update hit your site: what it means and what to do](https://porteur.ai/guides/google-core-update): Dropped after a Google core update? Check the dates, rule out spam or manual actions, and work a focused content plan. Here is how recovery happens. - [Google spam updates: the policies they enforce and how to stay clear](https://porteur.ai/guides/google-spam-update): See what a Google spam update enforces, the policies that trip small product sites, how to check your risk, and how to recover if you’re hit. - [Manual actions and the reconsideration request](https://porteur.ai/guides/manual-actions-and-reconsideration): Tell a Google manual action from an algorithmic drop, fix the cause, use disavow only when needed, and write a clear reconsideration request. - [The disavow tool: what it is for, and why you almost never need it](https://porteur.ai/guides/disavow-tool): You almost never need the Google disavow tool. Use it only for a link manual action or unremovable paid links. Here is how to decide and proceed. - [Ranking](https://porteur.ai/glossary/ranking): What a Google ranking is, why it varies, how to measure it in Search Console, and what to do when features above the results take clicks anyway. Want a second view while you wait, with three concrete leads, free in about thirty seconds? Paste your URL and get a check that reads your site and its search rivals. Free check: https://porteur.ai/