Page and indexable-URL count
ResolvedWe reviewed the old site URL by URL and explained which pages were retained, added, or intentionally retired.
Here is what changed after the July 24, 2026 evaluation and how we addressed each concern raised in the report.
The six items below follow the order of your report. The details and measurements are included in the corresponding sections.
We reviewed the old site URL by URL and explained which pages were retained, added, or intentionally retired.
The established pages now open normally, and alternate URLs redirect to the correct destination.
The established public URLs remain unchanged, including the Chicago and Berwyn examples in the report.
A page-by-page comparison shows that the migrated pages retained virtually all of their original copy.
Yoast is now active, the existing SEO settings were transferred, and standard structured data is present.
The SEO titles are now in place. Eleven same-topic page pairs from an earlier SEO approach are ready to be combined.
These figures summarize the work completed after the audit.
For each finding, we explain what caused it, what we changed, and what the site does now.
Original concern: staging showed roughly 23–30% fewer URLs, without an explanation of what was removed or why.
We reviewed all URLs on the old site. The 23–30% difference did not represent a corresponding loss of useful, indexable content. The original total included pages that were already set to noindex, old campaign pages, Spanish content being handled separately, and pages that had not yet been added to staging. We also found and added six ebook pages.
These figures come from the page-by-page review completed after the audit.
Original concern: would the extra redirects and missing pages still happen after launch?
The extra 404s and 301s were a staging issue, not the intended launch behavior. When your crawl ran, the existing page addresses and redirect list had not yet been connected to the rebuilt site. They are now connected, and the pages covered by this migration have been checked individually.
The 500 responses did not recur in follow-up testing.
Original concern: established flat or nested public URLs appeared to be moving under /practice-area/ and /location/.
We agreed with this recommendation and kept the established public URLs. The rebuilt site can use a cleaner structure inside WordPress without changing the addresses already known to users and search engines.
Each migrated practice and location page was matched to the exact address it uses on the live site. Page links, social-sharing information, and structured data now use that established address.
Users and search engines will continue to see the familiar URLs. The new practice and location organization stays behind the scenes and does not change the public address.
Original concern: the redesign appeared to have much less written content than the current site.
The page copy was not broadly cut during the redesign. We compared the old and new versions of 618 practice and location pages. The old pages contained 485,136 words and the new pages contained 483,492—a difference of 0.3%. On 615 of the 618 pages, the word count stayed within 5% of the original.
The Word Count Evaluation included both article copy and reusable Divi template text. The new design contains less repeated template text, which accounts for much of the difference.
In our July 26 follow-up capture, the old Divi page rendered 2,808 words and staging rendered 1,805. The actual Berwyn article was 1,481 words on both sites, and we rechecked that text directly. In other words, the old template added about 1,327 words around the article while the new template added about 324. The 1,003-word difference came from the templates—not the Berwyn copy. The same pattern appeared in the headings: the rendered pages had 59 versus 26, while the article itself had 13 on both. The difference was sitewide labels such as “Shop,” “FAQ,” and “Join Our Newsletter.”
The rendered totals are from the July 26 follow-up capture. The article text was rechecked directly against the old and new WordPress records on August 4 and is identical.
Original concern: staging exposed only a small fraction of the structured data found on production.
The crawl ran before the SEO plugin had been activated on staging. Yoast is now active, and the titles, descriptions, indexing settings, and standard structured data from the old site have been carried into the rebuild.
Original concern: staging showed 30 repeated title tags and 30 repeated H1s, including two Cook County car-accident pages.
There were two separate causes:
For each pair, one page and URL will be selected as the primary version. Useful content from both pages will be combined into that page, and the alternate URL will redirect to it. This will leave one complete page for each topic, with one title, one H1, and one URL for search engines to index.