Who Needs Enterprise SEO Consulting? The Signs That Say You Do

Most of the enterprise SEO consulting proposals I read do not deserve the fee attached to them. I say that as someone who sells the service. Since 2012 I have sat with companies that genuinely needed outside help, and with companies that needed nothing more than a verified Google Business Profile and a little patience.
So treat this article as a filter rather than a brochure. I will name the reports you open, the numbers Google publishes, and the point where paying someone becomes cheaper than guessing. If your site sits below those lines, keep the money and spend it on something that moves.
What is enterprise SEO consulting, and who actually needs it?
Enterprise SEO consulting means outside expert work on search visibility for sites whose scale, structure, or risk goes past what an internal team can safely handle: large catalogs, several languages, a migration, or a penalty. Google publishes the thresholds that separate those cases from ordinary sites, and most companies sit well below them.
The word enterprise does the real work in that sentence. A twelve page site and a catalog of four hundred thousand product URLs both live in Google Search, yet they fail for completely different reasons. The small one usually fails because nobody searches for what it sells. The large one fails because Google never finishes reading it.
Therefore the question is never whether search matters. It is whether your particular failure needs a specialist, a copywriter, or simply more months. That gap between failure types is the entire reason enterprise SEO consulting exists as a separate craft.
How do I know whether my company needs enterprise SEO consulting?
Start from the floor, because the floor is lower than agencies like to admit. Google lists only three technical requirements for a page to qualify for indexing, and clearing them costs nothing:
- Googlebot is not blocked from the page.
- The page works, meaning Google receives an HTTP 200 success status code.
- The page has indexable content.
Google also notes that clearing those three makes a page eligible for indexing, which is not the same thing as indexed. That distinction explains most of the panic in my inbox. Moreover, if the real problem is that almost nobody searches for what you sell, no amount of markup repairs it.
My first question to a prospect is therefore never about rankings. I ask which Search Console report they opened this month. If the answer is none, we are not ready to discuss a retainer; we are ready to read data together for twenty minutes, free. You can see how I frame paid work on my SEO consulting page.
When does Google itself say you should hire an SEO?
Google names a specific moment, and it is not the moment most companies choose. Its guide says the best time to hire is when you are considering a site redesign, or planning to launch a new site, and it adds that the earlier the better. In other words, before the damage rather than after it.
That single sentence has saved my clients more money than any audit I have written. A migration decided inside a design meeting, with nobody mapping old URLs to new ones, costs months of traffic. Consequently I would rather bill four days of planning than six months of recovery. My full playbook sits in how to protect SEO during a website redesign.
Notice the inverse as well. If you have no redesign, no launch, no migration, no penalty and no drop, Google names no urgent trigger at all. Waiting is a legitimate strategy, and it costs nothing.
The free checks that come before any quote
Before you pay for a diagnosis, run Google's own diagnostics. Each report below sits inside Search Console, costs nothing, and tells you which kind of problem you actually have:
- Performance report: clicks, impressions, CTR and average position, broken down by query, page and country.
- Pages report: which URLs Google indexed, with a reason for every exclusion.
- URL Inspection: the live status of one URL, plus the rendered HTML that Googlebot received.
- Core Web Vitals report: field data from real visitors.
- Sitemaps report: submission errors and read dates.
- Manual Actions and Security Issues: penalties and hacked content.
Consequently a consultant who cannot point at a specific line in one of these reports is guessing at your expense. Enterprise SEO consulting should begin where these seven reports end, not before them. I open all of them in the first call, share my screen, and let the client read the same numbers I read. Google documents each one in its Search Console starter guide.
What does Discovered, currently not indexed mean, and is it serious?
This status carries more information than any other line in the report. Google defines it as a page that was found but not crawled yet. Then it explains the usual cause plainly. Google wanted to crawl the URL, yet expected that request to overload the site, so it rescheduled the crawl.
Read the second half again, because it is a structural verdict rather than a content complaint. Your hosting, your internal linking, or the sheer number of low value URLs convinced Google that reading more of your site was not worth the load. Publishing another blog post changes nothing here.
So this is one status where I do recommend outside help early. The fix touches server response times, sitemap segmentation and URL pruning at once. Google also counts a large portion of URLs in this state as a signal that your site belongs in its crawl budget guide.
What should you do about pages stuck in Crawled, currently not indexed?
Google's definition is deliberately unhelpful, and that is the lesson. The page was crawled by Google but not indexed, it may or may not be indexed in the future, and there is no need to resubmit the URL. No button, no ticket, no escalation path exists.
In practice this status means Google read the page and judged it not worth keeping. Duplication is the usual culprit: three product URLs carrying the same description, or a paginated archive repeating its parent. Thin template pages come second, especially service pages that differ only by a city name.
My rule here is commercial rather than technical. Export the affected URL list, intersect it with the pages that actually produce revenue, then ignore the remainder. If forty blog tag pages sit in that list, fine. If your best category page sits there, you have a problem worth paying to solve.
Why does Google choose a different canonical than the one you set?
Because a canonical tag is a suggestion rather than an order. Google describes this status as a page marked canonical for a set of pages, where Google thinks another URL makes a better canonical. If you declare no canonical at all, Google decides which version is objectively best for users.
Its signals also differ in strength. A redirect is a strong signal that the target should be canonical. A canonical link element counts as a strong signal too, while inclusion in a sitemap is a weak one. Therefore listing a URL in your sitemap will never outvote a redirect pointing somewhere else.
The diagnostic Google recommends takes about ten minutes. Compare three URLs in the URL Inspection tool: the current page, the canonical you chose, and the canonical Google chose. Duplicate pages must also carry genuinely similar content, otherwise Google ignores the canonical you declared.
At what site size does crawl budget become a real concern?
Google answers this directly, and the answer disqualifies most sites. Does your site have few pages that change rapidly? Do your pages get crawled the same day you publish them? Then you do not need the crawl budget guide at all.
For the sites that do qualify, Google names three profiles:
- Large sites above one million unique pages with content that changes moderately often, about weekly.
- Medium or larger sites above ten thousand unique pages with very rapidly changing content, daily.
- Sites where a large portion of total URLs appear in Search Console as Discovered, currently not indexed.
Then comes the caveat that matters most: Google calls these rough estimates to help you classify your site, and states that they are not precise thresholds. So a nine thousand page shop with hourly stock changes still counts. Crawl budget is the clearest quantitative case for enterprise SEO consulting, and you can verify your own numbers against Google's crawl budget guide.
How do filters and faceted navigation burn your crawl budget?
Every filter combination mints a new URL, and Google explains the consequence without hedging. Crawlers usually access a large number of faceted navigation URLs before deciding those URLs are useless. Meanwhile crawl spent on useless URLs leaves less time for the new and useful ones.
Google lists four remedies, and each one fails differently when applied carelessly:
- Block filter URLs in robots.txt, with a rule shaped like disallow: /*?*products=.
- Move the filter mechanism onto URL fragments, which has no crawl effect at all.
- Use a canonical link element, which can reduce crawl volume on non canonical versions over time.
- Use nofollow, which only works if every link pointing to that URL carries the attribute.
Notice the trap in the last one. One forgotten template link and the whole effort collapses, which is precisely why large catalogs pay for this work. My notes on structuring a big catalog sit in category structure for large websites, and you can draft rules with my robots.txt generator.
What are the Core Web Vitals thresholds, and where does your site fall?
Get these numbers right, because half the audits I review quote them wrong. Search Console grades three metrics at the 75th percentile of page loads, segmented by mobile and desktop, using field data from real visitors instead of a lab score.
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| LCP, largest contentful paint | 2.5 seconds or less | 4 seconds or less | over 4 seconds |
| INP, interaction to next paint | 200 ms or less | 500 ms or less | over 500 ms |
| CLS, cumulative layout shift | 0.1 or less | 0.25 or less | over 0.25 |
Two details decide whether the report deserves your budget. Search Console groups URLs into pages with a similar user experience, and a group inherits the status of its worst metric. Also, Google states there is no single signal for page experience; its core ranking systems look at a variety of signals. The thresholds live in the Core Web Vitals report documentation.
What does an empty Core Web Vitals report tell you?
It tells you traffic is too thin to measure, not that your site runs fast. Google is explicit here: a URL group without enough data for LCP and CLS will not appear in the report, and Search Console then falls back to a higher level origin grouping.
Consequently a speed sprint is the wrong purchase for a low traffic site. You would optimise a metric that nobody has generated yet. Demand comes first, so the money belongs in keyword and offer work instead, which I describe in how to find keywords that drive sales.
I say this to at least one prospect a month, and it costs me work every time. Still, enterprise SEO consulting cannot manufacture demand, and selling a performance project to a site with forty daily visitors is closer to theatre than advice.
Does Google index your mobile site or your desktop one?
Google uses the mobile version of a site's content, crawled with the smartphone agent, for indexing and ranking. So whatever your phone layout hides, your rankings lose. Four parity rules carry most of the risk:
- The same primary content on mobile and desktop.
- The same structured data on both versions, prioritising breadcrumb, product and video markup.
- The same robots meta tags, since a mobile only noindex quietly removes the page.
- Equivalent title elements and meta descriptions across both versions.
One further rule catches modern front ends: never lazy load primary content on user interaction. Google does not scroll, click or type, therefore content hidden behind a tap does not exist for indexing purposes. That single mistake explains several of the worst traffic collapses I have investigated.
Can Google see the content your JavaScript renders?
Sometimes, and the delay is the real problem. Google processes JavaScript applications in three phases, crawling, rendering and indexing, and the renderer executes your scripts only on pages returning a 200 status code. Indexing then uses the rendered HTML rather than your source markup.
Between crawling and rendering sits a queue. Google's wording deserves memorising: a page may stay in that queue for a few seconds, though it could take longer than that. For a news publisher or a fast moving shop, longer than that translates into lost revenue.
Google also lists the mistakes it sees most often: URL fragments instead of proper redirects, multiple injected canonical tags, noindex added dynamically, badly lazy loaded images, and APIs that Googlebot cannot execute. My wider take on this sits in technical SEO after AI.
How do you test what Google actually sees without paying anyone?
Open the URL Inspection tool or the Rich Results Test, then read the rendered HTML. Google recommends exactly this to confirm that your content appears to crawlers. Search that output for four things: your main copy, your internal links, your canonical tag and your structured data.
If any of the four is missing, you have found a genuine and expensive problem in fifteen minutes, free of charge. If all four appear and traffic is still flat, your issue is demand or competition, and no technical retainer will touch it.
That test also protects you from bad proposals. An agency claiming your site is invisible to Google, while the rendered HTML clearly shows your content, is selling fear. Verify the claim yourself before signing anything; my schema generator helps with the markup half of that check.
Your traffic dropped after a core update: what does Google advise?
Patience first, and the timeline is official. Google recommends waiting at least one full week after a core update finishes before you analyse your site in Search Console. Then look at the site as a whole and try to stay objective about whether your content is helpful and reliable.
Google also warns against quick fix changes, such as removing a page element because you heard it was bad for search. Recovery can take months, because its systems need time to learn and confirm that the site now produces helpful, people first content. Sometimes recovery waits for the next core update entirely.
So the honest answer is that nobody can promise you a date. What an outside pair of eyes buys here is objectivity, since owners rarely rate their own content harshly. Read Google's page on core updates before you accept anyone's recovery plan.
How do you find out you have a manual action, and how does it come off?
Open Search Console, then Security and Manual Actions. One entry there explains a collapse better than any theory, because the report names the issue, the affected part of your site, and where to read more. Hacked content appears in the neighbouring Security Issues report instead.
Removal follows an unforgiving rule. Partial fixes earn no partial recovery. Therefore you find the issue across every affected page and correct all of it. Confirm with URL Inspection that those pages stay reachable, then file one reconsideration request and document what you did.
Timing matters too: most reconsideration reviews take a few days to a few weeks, and resubmitting before a reply only slows things down. This is the single scenario where I tell people to hire someone immediately, whoever it is. Guessing here extends the outage, and the outage is the cost.
Why is a migration the strongest reason to buy enterprise SEO consulting?
Because the rules are strict, and every one of them breaks easily inside a design sprint. Google recommends server side permanent redirects, specifically 301 and 308, and forbids redirecting many old URLs to one irrelevant target such as the new home page. One to one mapping is the whole job.
Then there is duration. Keep redirects in place as long as possible, generally at least one year, so Google can transfer every signal to the new URLs. If the domain or subdomain changes, the Change of Address tool applies, and its signal continues for 180 days after you start the move.
After that window Google recognises no relationship between the old and new sites, and treats the old one as unrelated. Expect ranking fluctuation during the move as well; a medium site can take weeks or more to settle. Test your rules with my redirect checker before launch day.
How do you verify hreflang on a multilingual site?
Take one page, list its full hreflang set, then check four things: mutual links, self reference, x-default, and code format. Google's rule is absolute, because if two pages do not both point to each other, the tags will be ignored. Each language version must list itself alongside all the others.
Codes break clusters just as often as missing return links. Use ISO 639-1 for language, optionally ISO 3166-1 Alpha 2 for region, as in en-US or de-CH, and remember that you cannot specify a country code alone. EU and UK are invalid region codes, whatever your marketing deck claims.
Also drop automatic redirection by IP or browser language, which Google advises against, since that pattern can prevent proper crawling of your variations. Build the tags with my hreflang generator, and read what the hreflang tag is for the full detail.
Country domain or subdirectory for an exporting site?
Google lays out the trade offs instead of choosing for you. A country specific domain gives clear geotargeting and makes server location irrelevant, yet it costs more and can target only one country. Subdomains and subdirectories under a generic domain are easy to set up, and subdirectories keep maintenance low.
One option Google explicitly does not recommend is a URL parameter such as site.com?loc=de. Remember also that Google determines a page's language from its visible content rather than from a declaration in your code, so a half translated template confuses it badly.
My default for exporters is a subdirectory per language, because a single host keeps maintenance cheap and signals consolidated. This site runs exactly that way. For a large catalog, pair the decision with e-commerce consulting and plan the sitemap split early, since one file caps at 50 MB uncompressed or 50,000 URLs. My XML sitemap generator handles the small cases.
Which company profiles need enterprise SEO consulting, and which do not?
The table maps profiles onto Google's published triggers rather than onto my invoice. Find your row, then read the last column first, because that column lists work you should never outsource.
| Company profile | Need level | Google trigger | First priority | Keep in house |
|---|---|---|---|---|
| Single location local business | Low, project based | Three technical requirements only; no paid local ranking | Verify the Business Profile | Hours, categories, photos, review replies |
| Multi location chain | Medium to high | Separate properties per unit; site diversity rarely shows more than two results per site | Location page architecture and canonicals | Each branch profile and its reviews |
| E-commerce with filters and variants | High | Above 10,000 pages changing daily, or 1 million weekly; faceted crawl waste | Faceted navigation and crawl control | Product copy, photography, campaigns |
| B2B services company | Medium | Trust matters most inside E-E-A-T; the Who, How, Why framework | Author bylines, sources, proof of expertise | Case studies, references, blog writing |
| Multilingual exporter | High | hreflang needs mutual links; invalid codes break a cluster | hreflang audit and x-default | Localised copy and translation quality |
| Large enterprise site in migration | Very high, as early as possible | Hire when considering a redesign, the earlier the better; keep redirects at least a year | One to one URL map with 301 or 308 | Content transfer checks, link text |
Can a single location business run its own local SEO?
Yes, and Google removes the excuse for outsourcing it. Creating and verifying a Business Profile costs nothing, the steps are documented, and Google states there is no way to request or pay for a better local ranking. Relevance, distance and prominence decide the order.
Every step that moves prominence is owner work:
- Verify ownership, which tells Google you are authorised to represent the business.
- Keep the full address, correct category and special hours current.
- Add attributes such as parking or wireless internet.
- Reply to reviews, which shows customers you value their feedback.
- Add photos and videos that show what you offer.
So if you run one shop in one city, spend the budget on photography and review replies rather than a retainer. I explain the mechanics in how to do Google Maps SEO, and most owners finish that work in a weekend.
What should you ask a consultant, and which answers are red flags?
Google publishes the questions, which is convenient for you and uncomfortable for weak vendors. Ask these, roughly in this order:
- Can you show examples of previous work and share some success stories?
- Do you follow the Google Search Essentials?
- What results do you expect, in what timeframe, and how do you measure success?
- How much experience do you have in my industry, my country and my city?
- What is your experience developing international sites?
- How will we communicate, and will you share every change you make to my site?
The warning signs are equally official. Nobody can guarantee a number one ranking on Google, so a guarantee disqualifies the vendor by itself. Be wary of anyone claiming a special relationship with Google or advertising priority submission. The same goes for cold emails, vague answers about the actual work, link popularity schemes and submissions to thousands of search engines. Google's guide on hiring an SEO lists all of it.
When hiring is simply a waste of money
Three situations, and naming them costs me work. First, a site under a few hundred pages with no manual action, no migration and no traffic drop; a monthly fee rarely finds anything there. Second, a brand nobody searches for yet, because visibility follows demand rather than tags.
Third, a company that will not change anything. I have written reports that sat unread for a year, where the fee bought nothing but a PDF. So before you hire anyone, including me, decide who will implement the recommendations and by when.
If you do cross the lines in this article, the first hour should cost you nothing but attention. Send your Search Console screenshots through the contact page and I will tell you plainly whether enterprise SEO consulting earns its price in your case, or whether patience would serve you better.




