Troubleshooting
"It says it wrote it, but my page has not changed"
In order of likelihood:
- Rank Math has never been set up. Until its setup wizard has been completed, Rank Math renders no metadata at all — not ours, not its own, not anybody's. Everything Metaly writes is stored correctly and none of it appears. Finish the wizard under Rank Math → Dashboard and it all shows up at once.
- Two SEO plugins are active. One holds the value, the other renders the tag. The coverage screen warns about this when it detects it. Deactivate one.
- A cache is serving the old page. Page caches, CDNs and object caches all do this. Purge and re-check.
- Your SEO plugin's template is winning. Some templates override a written field in certain conditions. Check the field in your SEO plugin's own meta box — if the new value is there, Metaly did its job.
Settings → Check the SEO plugin connection distinguishes these: it fetches the rendered page and tells you whether the value reaches it.
"Some items were skipped"
A skipped item means the field changed between when you chose it and when the run got to it — almost always because you edited it by hand in between. Your edit is kept and ours is withheld.
The review queue shows both values for those rows and lets you write ours after all, one row at a time. There is no bulk override: replacing something a person wrote by hand is a decision about one field.
A run that seems stuck
Runs move on WordPress's scheduler, which only advances when your site gets traffic. A quiet site can leave a run apparently paused; visiting the site moves it along. If your host has disabled WP-Cron in favour of a real cron job, make sure it is actually running.
"Paused — no items left this period"
The run has used the quota on your plan. What has already come back is still yours to review and apply — nothing is thrown away. The run resumes when the period rolls over.
Coverage numbers that look wrong
Two usual causes. First, post types you did not mean to include — check Settings, and see Coverage for why a shop's attribute stubs can dominate the number. Second, the template-fallback question, which has its own section on that same page: a page that renders a description can still correctly be reported as missing one.