Google Big Daddy Update (December 2005): What It Was and What It Means Today

The Google Big Daddy update was an upgrade to Googlebot and Google’s data centre infrastructure, rolled out from December 2005 to around March 2006. It changed how Google handled URL canonicalisation and redirects, including 302s, and some sites dropped out of the main index where Google had little trust in their links. The takeaway: Big Daddy was about crawling and indexing plumbing, so the fixes are technical: one URL per page, correct redirects and links you can stand behind.

Big Daddy is one of the infrastructure changes in my full list of Google algorithm updates. Unlike most named updates, it was not mainly a change to how pages were scored. It changed the system that collected and organised them.

What the Big Daddy update changed

Matt Cutts described Big Daddy on 22 March 2006 as “a software upgrade to Google’s infrastructure”. The changes reported across the update histories fall into two groups:

Canonical URLs and redirects

Wikipedia lists Big Daddy as changing URL canonicalisation, redirects and related items. In practice this was about Google deciding which of several addresses for the same page was the real one (for example example.com versus www.example.com), and how it treated 302 (temporary) redirects. At the time, 302 redirects were a known source of problems, including other sites appearing to “take over” a page’s listing.

Index inclusion and link trust

During the rollout, some sites found that many of their pages were no longer in Google’s main index. Cutts explained that the affected sites he looked at “had very low trust in the inlinks or the outlinks of that site.” In other words, pages were crawled less deeply where the links pointing in, or going out, looked untrustworthy: reciprocal link swaps, off-topic link pages and similar patterns.

Timeline

• December 2005: the new infrastructure began appearing at Google data centres. Only the month is recorded.
• Early 2006: more data centres switched over; webmasters reported pages dropping from the main index.
• 22 March 2006: Matt Cutts posted that only one or two data centres remained to switch over.
• Around March 2006: rollout treated as complete. Cutts said he would share more technical details after the full rollout.

Who was affected

As reported, two groups felt it most. First, sites with canonicalisation and redirect problems, where Google had previously been coping with messy URLs in a different way. Second, sites whose inbound or outbound links Google trusted little, some of which saw pages drop out of the main index. Sites with clean URLs and ordinary, earned links generally reported little change.

How to tell if the Big Daddy update hit your site

Big Daddy-type problems show up as indexing problems, not ranking problems, and today you can see them directly. This is how I would check a site for the same pattern:

1. Compare indexed pages with the pages you actually have. In Search Console’s Page indexing report, look at the count of indexed pages against the number of URLs in your sitemap. A large gap is the first sign.
2. Read the “Why pages aren’t indexed” reasons. “Crawled, currently not indexed” and “Discovered, currently not indexed” in large numbers often mean Google does not see enough value or trust to index everything.
3. Test redirects. Run your old URLs and domain variants through a redirect checker. Look for 302s used for permanent moves, chains of several hops and loops.
4. Check canonical choices. Use URL Inspection on key pages and see whether Google’s selected canonical matches the one you declared.
5. Review outbound links. Big Daddy is one of the few updates where outbound links were mentioned. Crawl your site and list external links; pages of unrelated links are worth removing.

How to recover from the Big Daddy update

Google did not publish a recovery guide for Big Daddy; Cutts promised technical details after rollout, but no single guide followed. The practical fixes that emerged, and that still apply, are these:

Redirects and canonicals are where a lot of site migrations still go wrong, and they are a large part of my technical SEO services. If you are planning a redesign or a domain change, my SEO web design and development work builds the redirect map in from the start.

Is it still relevant today?

Big Daddy itself is history. Canonicalisation and redirect handling remain core indexing concerns, and they are still among the most common reasons I find for pages that will not rank: the content is fine, but Google is indexing a different URL, or not indexing the page at all. Google now gives clear guidance on 301s, 302s and rel=canonical, which was not available in 2005.

Frequently asked questions

Sources

• Matt Cutts: Bigdaddy status update, almost there
• Search Engine Land: Google algorithm updates
• Bruce Clay: Google updates, a history of SEO from 2000 to 2010
• Wikipedia: Timeline of Google Search

If pages are falling out of Google’s index or your traffic dropped after a migration, request a free audit. My SEO audit service checks indexing, redirects and canonical signals and tells you what to fix first.