A high SEO-plugin score does not tell you whether a visitor can verify your claims, follow useful links or find a working image. This case study documents a focused technical SEO cleanup on ShazzSEO on 19 October 2026. It covers the problems found, the changes implemented and the checks used to verify them.
Project outcome: 55 contextual internal links were added across 30 published articles. The homepage’s competing structured-data definitions were consolidated, its case-study link was corrected, and 15 broken image addresses plus one outdated article address were mapped to their existing destinations. These are implementation results. This case study does not claim a traffic increase or a ranking improvement from changes made today.
The website and the objective
ShazzSEO is the SEO consultancy and publishing website of Shahzaib Ul Hassan. At the start of this review, WordPress contained 236 published posts and 112 published pages. The objective was to improve connections between useful articles, make the homepage’s evidence traceable, clarify its structured data and repair confirmed broken URLs without redirecting every missing page to the homepage.
The initial Rank Math site audit reported 95/100. The homepage was accessible, used HTTPS and had a self-referencing canonical. Those checks were useful, but they did not expose all of the editorial and implementation problems described below.
What the audit found
Area |
Before the changes |
Completed work |
|---|---|---|
Contextual internal links |
30 published posts without an explicit noindex directive had no internal links in their saved article content. |
55 relevant links added across those 30 posts. |
Homepage case-study evidence |
A traffic-growth claim linked to a booking calendar. |
The unsupported claim was replaced with a link to this implementation case study. |
Homepage structured data |
Two JSON-LD graphs repeated WebSite and WebPage IDs with competing publisher references. |
One Rank Math graph with separate Person and Organization entities. |
Broken images |
Some URLs used an incorrect upload year or filename capitalization. |
15 exact image-address redirects, plus corrections to affected saved content. |
Outdated article address |
An old website-builder URL returned 404. |
A permanent redirect to the current article, with its internal reference corrected. |
The original plugin report counted 44 entries without internal links. That was a different measure from the 30-post working list: plugin records can include other content types or previously indexed link data. The working list excluded posts explicitly marked noindex and inspected saved article HTML. Neither measure proves that a page has no incoming links from elsewhere.
Adding links where they help the reader
The linking work used the subject of each article to choose a destination. The proposal-software guide now connects the reader to discovery-call preparation and client onboarding. The onboarding checklist points to password management and measurement guidance. The WordPress plugin guide connects configuration advice to the WordPress SEO setup guide and internal-linking strategy.
Links were inserted beside relevant sections, using descriptive anchor text. Destinations were checked as published and without an explicit noindex directive before the changes were saved. An otherwise plausible destination was excluded when that check showed it was marked noindex.
For example, a reader comparing proposal tools can move from proposal software to SEO discovery-call questions, then into the client onboarding checklist. The links support the actual sequence of the reader’s work.
Making homepage evidence traceable
The homepage previously paired a percentage-growth claim and a 90-day statement with a booking-calendar link. The available material did not establish that specific result or timeframe. Publishing a new article repeating the numbers would not have supplied the missing evidence.
The replacement highlights a result that can be checked: internal linking repaired across 30 articles. The homepage links directly to this write-up. Its example search presentation is identified as illustrative, and the implementation counts are separated from any future search-performance results.
The homepage’s backlink sales card, backlink tab and panel, related navigation links and backlink FAQ were also removed as part of the requested homepage cleanup.
Resolving the homepage schema conflict
The homepage had both plugin-generated and template-generated identity markup. The same website and webpage appeared more than once, with different publisher references. One definition combined a person and an organization; another separated them.
The revised homepage uses a single Rank Math graph. ShazzSEO is the organization and website publisher. Shahzaib Ul Hassan is a separate person connected to the organization as its founder. WebSite and WebPage each have one stable identifier. This cleanup makes the markup internally consistent; it does not guarantee a rich result or a ranking change.
The starting 404 report contained 93 URLs and 144 recorded hits. The entries included broken image paths, an outdated article address, unpublished article slugs, missing optional files and automated requests for nonexistent PHP files. These categories require different responses.
A concrete example was the solar guide’s Sungrow image: the broken request used /uploads/2026/01/Sungrow-Solar-energy-300x246.png, while the existing media file was stored under /uploads/2025/01/. The saved article reference was corrected and the old image address was redirected to that same image. Equivalent checks found other incorrect year paths and a capitalization mismatch.
The outdated website-builder address had a clear equivalent at website builders for small businesses in Pakistan. That exact replacement received a permanent redirect. Retired entertainment URLs with no equivalent, scheduled articles and scanner requests were not redirected to unrelated content.
How the changes were checked
Verification covered the saved article content, destination publication status, live HTTP responses, homepage HTML and parsed JSON-LD. The homepage check looked for one WebSite and one WebPage definition, a working link to this case study and the removal of backlink sections. Redirect checks compared the response and Location header with the intended destination.
WordPress revisions and scoped backups preserve the earlier article content. Cache clearing was part of verification so the public page could be compared with the saved changes.
What these results do and do not establish
This work establishes that specific website defects were corrected. It does not establish that Google has recrawled every page, changed index coverage or rewarded the site with more traffic. At the audit date, Rank Math’s imported GSC performance table was empty and its stored URL inspections dated from 17 August 2026. Those records could not support a current before-and-after traffic comparison.
The next measurement step is to obtain current Search Console data and compare the affected pages over a suitable period, accounting for demand, query mix and other site changes. The GA4 and Search Console reporting guide explains the measurement context; the technical SEO audit checklist provides a broader diagnostic framework.
Practical lesson: connect each SEO recommendation to an observable defect, a specific change and a verification step. Report implementation outcomes immediately, and report search outcomes only when the data supports them.