Indexing Problems on a Law Firm Website

Arslan SEO Insights tells law firms that indexing problems happen when Google crawls a page but decides not to add it to search results, which is a separate step from crawling itself.

On law firm sites, this most often hits practice area and city pages that look too similar to each other, or pages that are too thin to be worth showing to searchers. Fixing it means making each page substantial and genuinely different, not just technically accessible.

Crawling and Indexing Are Not the Same Thing

A lot of confusion around this topic starts with treating "crawlable" and "indexed" as the same status. They're not. Crawling means Googlebot was able to visit the page and read it.

Indexing means Google decided that page was worth storing and potentially showing in search results. A page can be perfectly crawlable, with no technical blocks at all, and still never get indexed because Google judged it not worth including.

This distinction matters a lot for law firms, because the most common indexing failures on legal websites aren't caused by broken code.

They're caused by content decisions: too many similar pages, not enough unique value on any one of them, or a site structure that buries new pages where nothing links to them.

Why Law Firm Sites Are Especially Prone to This

Law firms, more than most other business types, tend to build large numbers of near-identical pages. This usually comes from one of two patterns.

The first is location expansion. A firm decides to target multiple cities or counties for the same practice area, like "car accident lawyer in [city]," and builds a page for each one.

If those pages share the same structure, the same stock content, and only swap out the city name, Google often treats them as duplicates of each other, picks one to represent the group, and leaves the rest out of the index entirely.

The second is practice area expansion done the same shallow way.

A firm handling several types of personal injury or mass tort cases writes a page for each one, but every page follows an identical template with generic language about "aggressive representation" and "fighting for your rights," with only the case type name changed.

Google's systems are built to detect this kind of pattern, and pages that read as interchangeable templates are among the most common candidates for exclusion.

Why Google Skips Indexing a Page

Thin or low-value content. A practice area page with a few generic paragraphs and no real detail about how that specific case type works, what compensation typically covers, or what the legal process looks like, may not get indexed even when nothing is technically broken.

Google's assessment of "is this worth showing" leans heavily on actual depth and usefulness, not just topical relevance.

Duplicate or near-duplicate content. A firm that builds a "car accident lawyer [city]" page for ten different cities using the same template with only the city name swapped often sees Google index one version, usually the one it judges strongest, and skip the other nine.

From the firm's perspective, nine pages simply vanish from search results despite being published and technically fine.

Canonical tags pointing elsewhere. A canonical tag tells Google which version of a page is the "real" one when duplicates might exist.

If a page has a canonical tag left over from a redesign, a migration, or a plugin misconfiguration, pointing to a different URL, Google will often index that other URL instead, even if the current page should stand on its own with its own content.

New pages that have not been discovered yet. A newly published page with no internal links pointing to it, and not included in the XML sitemap, may simply not be found.

Google has to discover a URL before it can crawl it, and discovery mostly happens through links and sitemaps. A page sitting alone with no path leading to it can go unnoticed for a long time.

Low overall site quality signals. Google doesn't evaluate a single page in a vacuum.

A site with many thin, templated pages can develop a lower overall quality impression that makes Google more conservative about indexing new pages from that same site, even ones that are individually decent.

This is one reason cleaning up old thin content often helps new pages get indexed faster.

Content that doesn't match search intent.

A page trying to rank for a broad term like "personal injury lawyer" but written as a generic overview with no real depth on damages, timelines, or the claims process may get crawled and simply judged not competitive enough to include, especially in a market where indexed competitor pages are far more thorough.

How to Check What's Actually Happening

Google Search Console's Page Indexing report (found under the Indexing section) labels every excluded page with a specific reason. This report is the starting point for diagnosing any indexing problem, and guessing without checking it wastes time on the wrong fix.

The most common labels seen on law firm sites are:

• "Crawled, currently not indexed." Google visited the page and chose not to index it. This is almost always a content quality or duplication issue, not a technical block.
• "Discovered, currently not indexed." Google knows the URL exists but hasn't crawled it yet, often because it's a low priority, poorly linked, or the site's crawl budget is being spent elsewhere.
• "Duplicate, Google chose different canonical." Google decided a different URL better represents this content and indexed that one instead.
• "Duplicate without user-selected canonical." Similar to the above, but the site never told Google which version to prefer, so Google picked one on its own.
• "Excluded by noindex tag." The page explicitly tells search engines not to index it, whether intentionally or by accident.

Each label points toward a different fix, which is why checking the actual report matters more than assuming.

What to Fix, Reason by Reason

For "crawled but not indexed," the fix is almost always making the page itself more substantial.

Add real detail specific to that case type or that city: what the legal process actually involves, what kinds of damages apply, what evidence matters, what deadlines exist under that state's statute of limitations.

Generic content padded with filler doesn't solve this. Google is judging depth and specificity, not word count alone.

For "discovered but not indexed," the fix is usually internal linking and sitemap inclusion. Add the new page to a relevant pillar page, like a main practice area hub that links out to every related case type or city page.

Confirm the page is included in the XML sitemap and that the sitemap itself is submitted in Search Console. Sometimes this alone is enough to get a page crawled and indexed within a few weeks.

For duplicate-canonical issues on near-identical city or practice area pages, there are two real options.

One is making each page genuinely different, with real local detail (nearby courts, hospitals, or highways for a city page) or real case-type detail (specific injury types, treatment patterns, or legal nuances for a practice area page) that couldn't be copied onto a different page by swapping a name.

The other is accepting that some pages don't need to exist independently and consolidating them into fewer, stronger pages instead. Not every city or every minor case variation needs its own page. Sometimes fewer, deeper pages outperform many thin ones.

For canonical tags pointing to the wrong URL, check the page's source code or use an SEO plugin's settings to confirm the canonical tag matches the page's own URL, unless there's a deliberate reason it shouldn't.

This is often a leftover technical issue from a site migration or theme change and can usually be fixed directly in the plugin settings without touching site code.

For sitewide quality concerns, the fix isn't a quick patch. It means auditing the whole site for thin, templated pages and either improving or removing them.

A smaller number of genuinely strong pages almost always outperforms a large number of thin ones, both for indexing and for actual rankings.

Real Examples of How This Plays Out

Picture a firm that expanded into five nearby cities over a year, publishing a "truck accident lawyer" page for each one.

Every page opens with the same paragraph about the dangers of large trucks, the same three bullet points about common causes of truck accidents, and the same closing call to action. Only the city name changes throughout.

Within a few months, Search Console shows four of the five pages as "Duplicate, Google chose different canonical," with only the original city page indexed.

The firm assumes something is broken. Nothing is broken technically. Google simply decided the pages weren't different enough to justify indexing all five.

The fix in a case like this isn't a plugin setting or a redirect.

It's rewriting each city page with real local specifics: the actual interstate or highway known for truck accidents in that area, the specific county courthouse where a case would be filed, local hospital trauma centers, and maybe even a mention of a well-known local intersection or stretch of road with a bad safety record.

Once each page has content that couldn't be copied onto a different city's page without becoming inaccurate, indexing usually follows within a few weeks of the recrawl.

A different, more technical example: a firm redesigns its website and migrates practice area pages to new URLs.

During the migration, the developer sets canonical tags on the new pages pointing back to the old URLs as a safety measure, intending to update them later, and then forgets to change them.

Months later, the firm notices new content isn't showing up in search at all. The Page Indexing report shows "Duplicate, Google chose different canonical" pointing to URLs that no longer even resolve correctly.

The fix here is purely technical: correcting the canonical tags to point to themselves, then requesting indexing once the tags are fixed.

Preventing Indexing Problems Before They Start

The cheapest way to deal with indexing problems is to avoid creating them in the first place. A few habits help:

• Before publishing a new location or practice area page, ask whether it says anything a different version of the same page couldn't also say. If the honest answer is no, the page needs more specific content before it goes live, not after.
• Link to every new page from somewhere relevant on the site, such as a practice area pillar page or a locations hub, before or immediately after publishing. Don't let new pages sit as orphaned URLs with no path leading to them.
• Keep the XML sitemap current and resubmit it in Search Console after major additions. Most SEO plugins update this automatically, but it's worth a periodic check.
• Audit canonical tags after any site migration, redesign, or platform change. This is one of the most common places for indexing problems to quietly appear, since the mistake is invisible to a normal site visitor and only shows up in technical reports.
• Resist the urge to build a page for every possible city and case type combination. A smaller number of genuinely useful pages beats a large number of templated ones, both for indexing and for how the site is perceived overall.

How Indexing Problems Affect Case Volume, Not Just Rankings

It's easy to think of indexing as a purely technical concern, but the real cost is missed cases.

A city page that never gets indexed can't show up in search results no matter how well it might otherwise have ranked, no matter how much content or link building goes toward supporting it.

If a firm invests in outreach, local links, or paid promotion pointing at a page that isn't indexed, that investment produces far less return than it should. Checking indexing status isn't just a technical housekeeping task.

It's a check on whether marketing spend pointed at a given page has any chance of paying off at all.

How Long It Takes to See a Fix Take Effect

After fixing an indexing issue, don't expect an immediate change. Google needs to recrawl the page to notice the fix, and recrawling doesn't happen instantly.

For a page with decent site authority and reasonable crawl frequency, expect a re-evaluation within a few weeks. For a page on a smaller or less frequently crawled site, it can take longer.

Using the "Request Indexing" tool in Search Console after a fix can speed up the recrawl, but it doesn't guarantee immediate indexing if the underlying issue wasn't actually resolved.

Indexing Problems Versus Ranking Problems

It's worth being clear about the difference between a page that isn't indexed and a page that's indexed but ranking poorly. These need different fixes, and mixing them up wastes effort.

If a page isn't indexed at all, it cannot rank for anything, no matter how well optimized the title tag or the on-page keywords are.

Google simply hasn't included it in the results it draws from. In this case, work on rankings is pointless until the indexing issue is resolved.

This is why the Page Indexing report should be the first thing checked when a page seems to be underperforming, before spending time on keyword adjustments or content tweaks aimed at improving rank.

If a page is indexed but not ranking well, the page is showing up in Google's results but isn't competitive enough for the specific search terms a firm cares about.

This is a different problem involving content depth relative to competitors, backlink authority, and overall site trust.

Confusing this with an indexing problem leads to wasted effort chasing the wrong fix, like resubmitting a sitemap over and over when the real issue is that three competitor pages simply have stronger content and more authority.

A Common Mistake: Requesting Indexing Without Fixing the Cause

A frequent mistake is repeatedly clicking "Request Indexing" in Search Console on a page that keeps getting excluded, without addressing the actual reason it's excluded. This doesn't work.

Google's systems evaluate the page's content and context again on recrawl, and if nothing changed, the same exclusion decision usually happens again. Requesting indexing is only useful after a real fix has been made.

What to Do If You're Not Sure Where to Start

If you've never checked your Page Indexing report before, start there before doing anything else. Log into Google Search Console for your domain, go to the Indexing section, and open the Pages report.

Look at how many pages fall under "Not indexed" versus "Indexed," and click into the "Not indexed" breakdown to see which specific reasons apply.

Sort by the reasons that affect your highest-value pages first, meaning your main practice area pages and any city pages tied to markets you actually want cases from.

A minor blog post sitting unindexed matters far less than a core practice area page that should be generating calls.

From there, work through the fixes reason by reason as outlined above, starting with anything labeled "Excluded by noindex tag" on a page that should clearly be public, since that's the fastest and most consequential fix available.

Then move to duplicate and thin-content issues, which take more time but usually deliver the biggest gains in visibility once resolved.

It also helps to confirm your XML sitemap actually lists the pages you want indexed and nothing else, since a stale or bloated sitemap can quietly make indexing problems worse.

Next Step

If practice area or city pages on your firm's site are not showing up in search despite being live, get a free audit from Arslan SEO Insights for a direct look at why.

You can also read about how a stronger law firm SEO foundation prevents these problems from building up in the first place.