ubricHelp

My score didn't change after a fix

Caching, JavaScript rendering and re-running: why a fix may not show up yet, and how to make it.

If your Rubric score did not move after a fix, the most common reason is that Rubric re-read the old page. Rubric reads what an AI engine reads, so a cached copy, or markup that only appears after JavaScript runs, scores exactly as it did before. Clear the CDN cache, confirm the fix in view-source, then re-run the crawl.

In short
  • →The usual cause is a cached page: Rubric re-read the old markup. Clear your CDN cache first.
  • →If the fix is injected by JavaScript, engines like ChatGPT, Perplexity and Claude never see it. Check view-source.
  • →Rubric does not auto re-crawl unwatched sites. Re-run the crawl manually, or add the site to your Watch list.

Why didn't my score change after a fix?

Rubric reads the live page exactly as an AI engine would, so your score only moves when the page an engine sees has actually changed and Rubric has read it again. Three things usually get in the way: the page is still served from cache, the fix only exists after JavaScript runs, or the crawl has not been re-run. Work through them in that order.

Did you clear the CDN cache?

This is the most common cause. Rubric reads what engines read, so if your CDN or platform is still serving a cached copy of the page, Rubric re-reads the old markup and the score is unchanged.

01
Purge the page from your CDN or platform cache after you ship the fix.
02
Purge every affected page, not just one. A template fix touches many URLs; a half-purged cache re-scores the old markup on the pages that were missed.
03
Give the platform a moment to rebuild before you re-run, so the fresh page is the one served.
Before you re-run
A half-purged cache is the quiet killer here. If a template-level fix seems to have worked on some pages but not others, it is usually because only some pages were purged. Clear the whole cache, then re-run.

Is the fix visible without JavaScript?

Render parity is whether the content an engine sees matches what a browser shows after scripts run. It matters because ChatGPT, Perplexity and Claude do not run JavaScript, Google does, and Microsoft Copilot renders it unreliably. If your fix (a block of schema, an answer paragraph, a heading) is injected by JavaScript, those engines never see it, and Rubric, reading like them, scores it as missing.

Test it with the view-source method:

01
Open the page and use "View source" (not the inspector, which shows the rendered DOM after scripts).
02
Search the raw HTML for your fix, for example the JSON-LD schema or the answer text.
03
If it is not in view-source, it is JavaScript-injected. Move it into the server-rendered HTML so it ships in the initial response.

The related article on rendering schema without JavaScript covers this in full.

Have you actually re-run the crawl?

Rubric does not automatically re-crawl every site on a schedule. There is no automatic weekly re-crawl of sites you have not added to your Watch list, so a fix will not appear until the page is read again. You have two ways to trigger that:

To see a changeDo this
Straight awayRe-run the crawl manually from the report or dashboard
Automatically over timeAdd the site to your Watch list, which re-checks it and can alert on changes

Re-run manually when you want to confirm a fix now. Use the Watch list for ongoing monitoring.

Common questions

Did this answer your question?