
In our experience, enterprise SEO budgets mostly go on new work, such as more content, a faster site or a launch in a new market. It feels like the obvious way to grow, because new work is easy to see and easy to sign off.
However, when visibility doesn’t rise to match, the cause is often older gaps in how the site is built and run, sitting underneath that new work.
Fixing what a site already has can bring significant returns, though it’s only part of the opportunity. Nature’s Best, a health retailer, came to us after its search performance had dropped, and our work started with a technical audit of the pages it already had. Over a 10-month period, its organic revenue rose 65.5% year on year, as our Nature’s Best SEO case study shows.
That work began with fixing what was already there. This article covers six common gaps that stop SEO spend turning into visibility on large sites, and how to close each one. Our SEO process starts with a technical, content and competitive review “to find what’s holding visibility back”.
Some gaps are quick to close, while others, such as lining up versions for several markets, take longer to fix. On an enterprise site, each one can grow unnoticed until it costs real traffic. That’s why we start with whichever gap affects the most pages.
1. International versions competing with each other
When a website serves several countries or languages, different teams may end up managing different markets on their own. Over time this can lead to inconsistent URL structures, duplicated content and international SEO that nobody coordinates. Search engines may then struggle to work out which regional version of a page to show, which can hold back visibility across markets.
The fix is to follow Google’s guidance on sites that serve several regions and languages. Google advises choosing a URL structure that makes geotargeting easy, meaning it’s clear which country each version is for, and giving each language version its own URL. These are the three main options, each with its own pros and cons in Google’s guidance.
- Country-specific domains: such as example.de. Google says these give clear geotargeting and easy separation of sites, but they can be expensive, need more infrastructure and can only target a single country.
- Subdomains on a generic domain: such as de.example.com. These are easy to set up and allow different server locations, though users may not know from the URL whether “de” means a language or a country.
- Subdirectories on a generic domain: such as example.com/de/, or folders that name both the language and the country, such as example.com/de-de/, example.com/en-gb/ and example.com/en-us/. These are easy to set up and low maintenance on one host, but separating the sites is harder. Naming the language and country in the folder makes the target easier to read from the URL.
Whichever structure you choose, tell Google about each language and regional version with hreflang, a tag that tells search engines which language, and optionally which country, a page is for. It can go in HTML tags, HTTP headers or an XML sitemap. Google says each language version “must list itself as well as all other language versions”, and that if two pages don’t both point to each other, “the tags will be ignored” (Google Search Central).
Google has also retired the International Targeting report in Search Console, so you can no longer set a target country there. Site structure and hreflang now do that job (Google Search Console Help).
That makes a well-planned site structure, correct hreflang and clear regional content especially important for businesses selling across several markets.
2. Retired pages piling up as 404 errors
Large sites retire products and content all the time because of stock, seasons or a change of focus. Each retired page that isn’t handled properly can become a 404 error, the “page not found” response. That’s a poor experience for anyone who arrives looking for something, because the page they expected has gone and nothing points them anywhere useful.
Google treats a 404 as a normal sign that a page no longer exists. It removes the URL from its index if it was indexed, and “the crawling frequency gradually decreases” (Google Crawling Infrastructure). So the real cost can be lost visitors, lost organic visibility and the value of any backlinks pointing to those pages.
Instead of dealing with each error as it comes up, agree rules for retiring pages and make them part of how your team publishes. These three rules cover most cases.
- Use a 301 redirect for a real replacement: when a page has been retired and a suitable alternative exists, use a 301 (permanent) redirect to the closest relevant page. Google uses a permanent redirect “as a signal that the redirect target should be canonical”, meaning the new page should become the version it shows in search (Google Search Central).
- Keep 302 redirects for temporary moves: Google follows a 302 (temporary) redirect, but its indexing pipeline “doesn’t use the redirect as a signal” that the new page should replace the old one. Only use it when the move really is temporary.
- Keep temporarily out-of-stock product pages live: don’t automatically remove or redirect a page when a product is only unavailable for a while.
Keeping an out-of-stock page live lets it hold on to its search visibility, backlinks and the signals it has built up while the product is away. Show a clear “Out of stock” message and point visitors towards similar or alternative products. Where you can, give an idea of when the product might return.
Don’t send large numbers of old pages to the home page. Google warns that redirecting many old URLs to one unrelated page “might be treated as a soft 404 error” (Google Search Central).
3. Broken internal links and redirect chains
Broken links are easy to lose track of on a large site, and redirecting every one of them isn’t an efficient fix. Each extra redirect makes users and crawlers take another step before they reach the page, so over time those steps join up into redirect chains.
Crawl budget is the number of pages Google can and wants to crawl on a site over a given time. How much crawl budget matters depends on the size of the site. Google’s guide is aimed at sites with 1 million or more unique pages that change about once a week, or 10,000 or more that change daily, and it calls these figures rough estimates (Google Crawling Infrastructure).
Google’s crawl budget guidance says to “avoid long redirect chains, which have a negative effect on crawling”. By default, Google’s crawlers follow up to 10 redirect hops (Google Crawling Infrastructure).
The best answer at scale is automation. When a URL is redirected, your system should update internal links to point straight at the new address. At the very least, run regular internal link audits so you catch problems early.
4. Paying for more content when the problem is quality
Pressure to publish more is common in enterprise teams, and generative AI makes it easy to produce large volumes quickly. More pages don’t always mean more visibility. Google’s spam policies include scaled content abuse, which covers “large amounts of unoriginal content that provides little to no value to users, no matter how it’s created” (Google Search Central).
Nature’s Best shows the other approach. Our technical audit found that many of its pages weren’t earning search visibility. We worked out where pages should be “removed, optimised or combined” and set a priority order for technical fixes, including the XML sitemap and page speed.
We also did new keyword research and gave its in-house writers a content calendar and SEO content briefs. That work ran alongside the technical fixes during the period when organic revenue rose 65.5%.
So before we plan new content for a large site, we check which existing pages should be improved, combined or removed. I’d argue that check matters more than any new publishing plan.
5. Relying on text alone
People take in information in different ways, so a site that only publishes text can miss part of its audience. Google’s guidance on its AI search features says “when it makes sense, look for ways to support your textual content with high-quality, relevant images and videos on your pages”. It adds that its generative AI search features can bring in relevant images and video (Google Search Central).
Text-only pages can also waste money already spent. A page that cost time and money to write can’t show its own image or video in search if it has none. That loses part of the return on the work.
A good first check is to list your top organic landing pages and mark which have no image, video or diagram that helps explain the content. Those pages already earn traffic, so adding a clear visual to them builds on work you’ve already paid for.
For new content, a useful habit is to ask how each written piece could work in another form, whether that’s a diagram, a short video or a simple interactive tool, since each one gives the page another way to appear in search.
6. Spending on speed before relevance
Speed work can take months of developer time, and faster load times alone don’t guarantee better rankings.
Page experience still matters, and Google says “Core Web Vitals are used by our ranking systems”. It also says Google Search “always seeks to show the most relevant content, even if the page experience is sub-par” (Google Search Central). Good scores help, but they won’t lift a page that doesn’t answer the search well. For that reason, I’d check relevance before approving any speed project.
Core Web Vitals are three measures of how a page feels to use.
- Largest Contentful Paint (LCP): how quickly the main content loads.
- Interaction to Next Paint (INP): how quickly the page responds to clicks, taps and key presses. INP became a Core Web Vital in March 2024, replacing First Input Delay (web.dev).
- Cumulative Layout Shift (CLS): how much the layout moves around while the page loads.
The Core Web Vitals report in Search Console groups pages with a similar experience. It rates each group good, needs improvement or poor, based on what 75% of visits experienced (Google Search Console Help). The thresholds are in the table below.
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| LCP | 2.5 seconds or less | 4 seconds or less | Over 4 seconds |
| INP | 200ms or less | 500ms or less | Over 500ms |
| CLS | 0.1 or less | 0.25 or less | Over 0.25 |
How to find the gaps in your enterprise SEO strategy
These steps will show which gaps affect your site, and in what order to close them.
- Check every international version: list each one and confirm it follows the agreed structure, with hreflang that lists itself and every other version.
- Export errors and chains: pull 404 errors and redirect chains from your crawler and from the Page Indexing report in Search Console.
- Agree rules for retired pages: decide how each retired page is handled, and check internal links point straight at final URLs.
- Audit content before commissioning more: look for thin, duplicate or underperforming pages first.
- Fix the worst page groups first: check the Core Web Vitals report and start with groups rated poor.
- Rank what you find: score each fix by commercial impact and effort, then compare it with the new work already planned.
The last step is where an audit turns into a plan. For Evolution Power Tools, our technical audit found 96 key technical issues, which we prioritised and split into quick wins and longer-term actions. Between August and November 2024, alongside on-page work and digital PR, search volume from page 1 keywords rose 68%, as our Evolution Power Tools SEO case study shows.
Where does your enterprise SEO stand?
Use these three stages to place your own site.
- Reacting: fixes happen when someone spots a problem, such as a drop in traffic or a broken page. Each market runs its own set-up and nobody owns retired pages.
- Managing: regular audits catch 404s, redirect chains and thin content. Fixes still compete with new work for developer time and often lose.
- Built in: rules for retiring pages, redirects and hreflang are part of how teams publish. New spend is weighed against fixes by impact and effort before it’s approved.
If you’re at the first stage, extra budget is likely to leak through the same gaps, so the steps above are the quickest way to reach the second.
Getting more from the SEO budget you already have
None of these gaps is unusual. Most come from the size and age of a site more than from any one mistake, and each can be closed with clear rules, regular audits and a plan the teams share.
Before adding budget, it’s worth checking how much of what you already spend is reaching Google and other search engines. If you’d like a second view of where your SEO budget is leaking and what’s worth fixing first, get in touch with our SEO team.
Frequently asked questions
Why isn’t SEO investment improving visibility?
On large sites, new SEO work often sits on top of older problems. Competing international versions, unhandled 404 errors, redirect chains and thin content can all absorb the value of new spend before it shows up in search.
What should an enterprise SEO strategy fix first?
An enterprise SEO strategy should start with the gap that affects the most pages. On a large site, a small fault repeated across thousands of URLs can add up to more lost traffic than a serious fault on a few.
Do 404 errors hurt SEO?
Not on their own. Google treats a 404 as a sign the page has gone and removes it from the index. The harm comes from lost visitors and backlinks, so redirect pages that have a close replacement.
Do Core Web Vitals affect rankings?
Yes. Google says Core Web Vitals are used by its ranking systems. It also says it shows the most relevant content even when page experience is poor, so speed work won’t make up for a page that doesn’t answer the search.
Can you still set a target country in Search Console?
No. Google has deprecated the International Targeting report in Search Console. Use hreflang and a clear site structure to show which version of a page is for which country or language.
References
These Google pages back the guidance in this article.
- Google Search Console Help, International Targeting report deprecated. Read 11th November 2026
- Google Search Central, Tell Google about localized versions of your page. Read 13th November 2026
- Google Search Central, Managing multi-regional and multilingual sites. Read 13th November 2026
- Google Crawling Infrastructure, How HTTP status codes affect Google’s crawlers. Read 11th November 2026
- Google Crawling Infrastructure, Optimize your crawl budget. Read 11th November 2026
- Google Search Central, Redirects and Google Search. Read 16th November 2026
- Google Search Central, Site moves with URL changes. Read 11th November 2026
- Google Search Central, Spam policies for Google web search. Read 11th November 2026
- Google Search Central, Optimizing your website for generative AI features on Google Search. Read 11th November 2026
- Google Search Central, Understanding page experience in Google Search results. Read 11th November 2026
- web.dev, Interaction to Next Paint becomes a Core Web Vital. Read 11th November 2026
- Google Search Console Help, Core Web Vitals report. Read 11th November 2026