WordPress engineering case study · Internal website · 26 October 2026

A real 13-page Rank Math schema cleanup: what we found, changed and verified

When we examined our own WordPress city pages, some declared videos they did not display and used review-oriented schema that did not accurately represent the page’s purpose. This is a record of a bounded correction—not a manufactured client success story or a ranking claim.

Publisher: Khalsa Website Designers, Kartarpur, Punjab. Prepared from authenticated WordPress database and live-page inspections conducted on 26 October 2026. Site operator’s own technical work; not independently certified.

13Commercial city pages checked and corrected
156Legacy VideoObject metadata entries removed (12 per page)
13Inappropriate rating-bearing schema records corrected across the combined work

These counts concern the specific audited WordPress records. They do not represent a whole-site cleanup, a Google penalty, or the number of ranking positions gained.

Follow-up on 26 October 2026: After the original 13-page investigation documented here, the same checks and rollback process were applied to eight further service pages: Kharar, Zirakpur, Khanna, Nawanshahr, Batala, Moga, Firozpur and Rajpura. Across both batches, 21 service pages have now been corrected, removing 252 obsolete VideoObject entries and 21 inappropriate rating-bearing schema records. These are technical output corrections verified on the live pages; no resulting ranking or enquiry increase has been established.

1. The problem: metadata did not match the landing pages

The inspected pages served website-design customers in cities such as Ludhiana, Chandigarh and Amritsar. Each page was primarily a service landing page, not a video watch page. Yet the stored Rank Math metadata included 12 VideoObject entries per page. Our review of rendered main content found no corresponding video embeds on the examined pages.

Some pages also contained rating-bearing CreativeWorkSeries markup; Ludhiana included a business-rating schema. These structures are not substitutes for genuinely relevant service details, and publishing self-controlled reviews about your own business as LocalBusiness or Organization markup does not qualify for Google’s review-star feature.

The error was an accuracy and search-feature eligibility concern. We did not establish that it caused ranking loss, a manual action, or any specific Google Search Console warning.

Google’s guidance: a video should be available to watch on its associated page, and structured data should describe the actual content. Read Google’s VideoObject guidelines and review-snippet rules.

2. The diagnosis: distinguish an obsolete record from a real video

Before — observed pattern

A service page reporting videos it did not show

  • 12 stored VideoObject entries on each audited page.
  • No corresponding visible video player in the inspected page body.
  • Legacy rated creative-work or business metadata on pages intended to explain website-design services.
  • Some old video descriptions were generic rather than specific to the page.
After — verified state

Accurate service and page information

  • No remaining VideoObject or rated creative-series records of the audited types on these 13 pages.
  • One relevant Service record per page.
  • The ordinary WebPage, WebSite and Organization graph still renders.
  • Existing page URLs, SEO titles, robots directives and canonicals preserved during the cleanup.

The investigation questions

  1. Which page is this? A service page, article, product page or actual video watch page?
  2. Which structured-data nodes are present in the final, live JSON-LD, rather than only stored in an SEO plugin?
  3. Can a visitor find and watch the videos declared in VideoObject markup?
  4. Are review claims made by customers, and does Google permit review stars for the entity being described?
  5. If a schema record is changed, will the site’s ordinary page and organisation graph survive?

3. What we changed—and why the order mattered

We used a small pilot, then expanded only after live verification. Before each controlled group of changes, we retained the original serialized Rank Math metadata. The goal was to make narrow, recoverable changes without altering the content that visitors use.

Stage Change Reason / check
Inspect Review source, rendered page and WordPress metadata Verify which video and rating nodes are actually present
Preserve Save copies of the original metadata values, including encoded snapshots where exact spacing mattered Keep a concrete restoration path before touching serialized data
Replace Remove inappropriate rated CreativeWorkSeries or page-specific business-review markup; add a truthful Service description Represent the service page’s actual purpose
Clean Remove only the obsolete VideoObject records, after the replacement schema was saved A Rank Math save had repopulated old video entries during testing, so the cleanup order was important
Verify Check stored records and the newly rendered JSON-LD, titles, canonicals and robots instructions Ensure both the inaccurate metadata and inadvertent regressions are absent
Implementation caution: during the pilot, removing the final custom schema record left one page without its expected generated JSON-LD graph. We restored a relevant Service record, rechecked the normal graph, and then cleared old video entries. This is why bulk-deleting all schema values or disabling Rank Math’s schema module was not an appropriate first move.

What the corrected service description means

Instead of declaring 12 unrelated videos, the affected pages now use a service description similar in structure to the following illustrative extract (not the entire live Rank Math graph):

{
  "@type": "Service",
  "name": "Website design and WordPress development for Ludhiana businesses",
  "serviceType": "Website design and WordPress development",
  "provider": {
    "@type": "Organization",
    "name": "Khalsa Website Designers",
    "url": "https://www.khalsa-website-designers.net/"
  },
  "areaServed": {
    "@type": "City",
    "name": "Ludhiana"
  }
}

Important: Service data describes the offering; it is not a promise of a Google rich result, higher search position, local branch office or independent accreditation.

4. The 13 pages and independently repeatable checks

The following pages were included in the controlled audit and correction. Their current source can be examined publicly; the internal backup records themselves remain private to WordPress administrators.

How to verify a page today

  1. Open one of the listed URLs in a browser and inspect its page source.
  2. Search for the application/ld+json block. Identify the page’s WebPage, Organization, and Service nodes.
  3. Check whether a VideoObject is present. If it is, look for a genuinely playable corresponding video rather than assuming it is wrong.
  4. Review the page’s canonical URL and robots meta directives, then compare the service description against what the page actually offers.
  5. Use Google’s Rich Results Test for supported rich-result eligibility and Schema.org Validator for general schema structure. These tools answer different questions.

Verification snapshot: authenticated database inspection, 26 October 2026. All 13 audited published pages retained a single stored rank_math_schema_Service record and none of the targeted legacy video, rated-series or page-specific LocalBusiness records. Live-page checks were conducted in controlled batches. A later update or cache state may alter what is visible.

5. A safer approach for other WordPress owners

Not every WordPress site should receive this particular change. Before removing any schema, identify which content it represents. A legitimate page with a playable video may benefit from correct video markup.

  1. Start with a reproducible mismatch. Capture the precise URL, source markup and visible content. Do not treat plugin versions alone as evidence of a fault.
  2. Make a recoverable backup. WordPress metadata can be serialized. Avoid raw string replacements that can corrupt stored arrays or change string lengths.
  3. Prefer the plugin’s supported editor. Rank Math documents ways to remove schema from individual posts and pages. Choose a targeted operation instead of turning off schema sitewide.
  4. Work on a test case first. Preserve canonical, robots, sitemap eligibility and existing page content.
  5. Recheck the final response. A record disappearing from the database is not sufficient; inspect the final JSON-LD after caching and page-builder effects.
  6. Measure later. Track any relevant Search Console search appearance and organic-query changes over time. Do not claim a ranking win from the correction alone.

Reference: Rank Math: Removing Schema from Posts and Pages. See also Rank Math’s documentation on schema templates.

Frequently asked questions

Does removing incorrect VideoObject schema make a site rank higher?

Not automatically. The correction can improve data accuracy and compliance with applicable search-feature guidelines. Search rankings also depend on the page’s relevance, usefulness, competition and many other considerations. We have not claimed a measured uplift from this cleanup.

Should every VideoObject entry be deleted from Rank Math?

No. Keep accurate video data for pages where visitors can actually watch the corresponding video. The audited entries were removed because the inspected service pages did not show their declared videos.

Does Service schema create a star rating or guaranteed rich snippet?

No. A factual Service description does not itself make a page eligible for Google’s review-star feature or guarantee any rich result.

Can a plugin conflict be diagnosed from the metadata alone?

No. Unexpected markup has multiple possible causes. Compare stored configuration, plugin output and the rendered page before assigning responsibility.

Is this a client case study?

No. It documents first-hand changes to Khalsa Website Designers’ own website. Any future client case study should use appropriate permission and accurately show what was delivered and measured.

Transparency: This article was compiled from the site’s own technical-change records with AI assistance and published by Khalsa Website Designers. It is not an independent security certification, an endorsement by Google or Rank Math, or a claim of client results. Corrections can be requested through our contact page. Read our editorial standards and work-evidence register.

Published 26 October 2026 · Evidence relates to the site’s state on that date.

Need a WordPress schema or indexing problem investigated?

Tell us the affected URLs, what the page actually contains, and the Search Console message if available. We can explain the diagnostic scope before proposing changes. For a new website or redesign rather than a repair, see our Punjab WordPress website design services. Do not include passwords, payment details or private customer data in an initial enquiry.

See technical SEO and indexing services

Related: WordPress repair services · PHP and plugin errors · Search visibility evidence

//
SSA Ji, My self Daljit Singh. Let's talk over WhatsApp chat or call.
How Can I Help You?