Fixes

Who does each fix

Every task says who does it, and the list can be narrowed to one group. Start with these, above the tabs, names the first few to do — the audit's own order, most points at stake first.

The steps are written for what your site runs on — WordPress (with Rank Math, Yoast or another SEO plugin), Shopify, Wix, Squarespace, Webflow, Ghost or a custom-built site. Each audit reads it from your home page; if it's wrong, choose the right one with Not right? above the list. On WordPress, a task Vidrys could do through the free Vidrys SEO plugin says so, with Set it up, above the steps — on Shopify, one the Vidrys app for Shopify would do; on Wix, one the Vidrys app for Wix would; on Squarespace, one a Squarespace connection would do on your product pages; and on a custom-built site or one already on Cloudflare, one a Cloudflare connection would.

Some tasks come with something to paste: a robots.txt that names your sitemap, your organisation's structured data, a redirect list in the form your platform imports (Shopify, Squarespace, Ghost, the WordPress Redirection plugin, Apache, Nginx, Netlify or Vercel), the links to change and what to change them to, or the Open Graph tags a page lacks. Show builds it from your latest audit; copy it or download it.

Sending fixes to your developer or host

Send to your developer or host (on a task, or Send the developer's list above the tabs) makes a link listing the tasks you choose: what's wrong, the pages, how to fix each and anything to paste, with a note from you. Whoever opens it needs no account. It stays up to date — a task they've fixed shows as fixed after your next audit — and works for 30 days. Copy the link or the ready-made message, or email it from your own email. Links you've sent are listed with how often they were opened, and Switch off ends one at once.

Technical, on-page and off-page

Under To fix, each row is a check the audit failed, most points on the table first, with how many pages it names and who does it: You, or Vidrys where the field is one it writes. Open a row for what to do, what the failing pages share when they share a cause (a title ending every page carries, a section heading the template marks as H1), and the first pages with what was found on each; Show all N pages lists the rest right there. Checks that pass overall but still name a few pages — three 404s on a large site — follow under Passing, a few pages left. The number on each tab counts its rows to do. Fix things, then Run audit again: a page that no longer fails leaves the list.

Pages to write

Get the brief on a keyword under What to work on next opens its brief here, and Pages to write on the On-page tab keeps every one you started with how far it has come: Brief → Draft → Publish → Rank. A brief is free. Generate writes a draft for one of the month’s SEO page drafts — SEO’s own allowance, not your content credits — and Content grade then scores it against the brief and against Google’s top results for the keyword, whose pages Vidrys reads with its own crawler once the results page is loaded: the keyword in the title, the opening and a heading; the searchers’ questions answered; the related keywords and the topics most top pages cover; length against theirs; sections, links to your other pages and image alt text. A brief that edits a page you already have grades the live page too, so you see where it stands before and after. The grade is free and moves as soon as the draft does. Publish sends the draft to your connected CMS or webhook — a new page is posted; an edit to a page you already have goes to a webhook as a change request — and the page counts as published once it is live; with nothing connected, put it live yourself and press Mark published. From then on the keyword is tracked against the page, and reaching Google’s first page counts as a win.

Fixes Vidrys proposes

With the Vidrys SEO plugin on a WordPress site, Vidrys also proposes fixes it makes as your pages are served — for what no page field holds. Those that come from the theme or the server are one fix for the whole site, checked on one page that had the problem:

With the Vidrys app for Shopify, its theme embed adds what your theme lacks once you switch it on: Open Graph tags on a product, collection, page or article without them, your organisation's structured data on the home page, and — read from your crawled pages rather than a scored check — Product structured data on product pages and breadcrumbs, when the crawl finds your product pages or store pages without them. An app can add tags but can't take your theme's out, so each is proposed only where the theme lacks it.

With a Cloudflare connection — for any site on Cloudflare, custom-built included — every fix above is served by a Worker on your Cloudflare account, and so is what only a server can do:

Proposals sit under the check they answer — the row says N to approve — canonical tags, noindex, redirects and links under Technical, titles, descriptions, alt text and Open Graph tags under On-page. A model-written proposal is marked AI: read it before approving. Model-written proposals arrive a few minutes after an audit, at most 20 a run, counted in your SEO daily spending limit; one you dismiss is not asked for again until the page itself changes. Check for new fixes looks again after an audit, for every field at once.

1. Press Review on a proposed fix. It reads the page from your CMS and shows what the page has now and what it would get.

2. Change the value if you want — a title, a description, an address, each image’s alt text. Titles need 15–60 characters and descriptions 50–160, what the audit asks for; the original proposal stays on the fix. Noindex removal has nothing to edit.

3. With the Vidrys SEO plugin, Preview on your site opens the page with the change on it — your edit included — seen only by you, while you're logged in to WordPress, for an hour. Visitors see the page as it is.

4. Press Approve & publish. Vidrys writes the value to your CMS, then reads the live page to confirm it is there: Published · checking, then Live. A redirect counts as live only when it is permanent and lands on a page that answers. (Approve dry run appears instead while fixes through your CMS run as dry runs — nothing is written.)

5. Not happy with it? Dismiss — that page and field are not proposed again. Changed your mind after publishing? Roll back restores exactly what was there before. Finished fixes move under Done by Vidrys.

A fix that replaces a value — a new title over an old one, say — is written only while the page still shows exactly the value it was proposed against, and while your CMS holds that value or none. If someone changed it since, nothing is overwritten: the fix says so and stops.

Page edits

Some fixes change a page's own text rather than a setting. Each waits for you — never applied without review — and shows as before and after: what the page has now, and what it gets. Change any words before approving, or leave an edit out.

Where it's made depends on what your site runs on: in the page's own text where your connection keeps it — a WordPress post, a Shopify product, collection, page or article — and, through the Vidrys SEO plugin or Cloudflare, as the page is served where the theme or a page builder (Elementor, Divi) prints the text. An edit is made only while the page's text still matches what the crawl read; if it changed, the fix stops and says so, and the next audit proposes it again from the page as it is. Rolling back puts the page's text back exactly as it was.

Apply without review

Tick a type under Apply without review and a proposal of that type is published the moment it is found, without waiting for you. Only what Vidrys takes from the page itself is offered: a missing title, description or canonical, Open Graph tags copied from the page’s own title and description, and mechanical corrections that say the same thing properly — a canonical written in full and over https, a link pointed at the address it already ends on — and, through the Vidrys SEO plugin, the page language, one title and description per page, the sitemap in robots.txt and hreflang links back. Each is still checked against the live page first, checked again after, reversible, and drawn from the month’s fix allowance. Model-written text, page edits, removing a noindex, redirects, a broken link’s new address (a guess), the HSTS header, a 404, one canonical per page, your organisation's data and rendered copies for crawlers always wait for you. Untick to go back to approving each one.

Off-page

Where to get links lists the pages to ask, each with what to do and who decides — the same list as under Backlinks; Why this page shows the reasons. Links you lost lists the sites that linked to you and no longer do: ask each one to restore the link, or to point it at the page’s new address.

Export tasks

Export tasks hands the work on to whoever does it. The list is every tab’s: checks the audit failed (with what to do and their pages), fixes waiting for review, pages to write from your briefs, and places to get a link. Choose a tab or All, then:

Up to 25 tasks go at once; one that fails is listed with why, and never stops the rest. To connect Trello, paste your API key, a token and the list id; for Jira, your site’s address, your email, an API token, the project key and the issue type. Vidrys checks them with Trello or Jira before keeping them, keeps them encrypted, and never shows them again. Viewers can download the CSV but not connect or send. Sending the same task twice makes a second card — Vidrys doesn’t follow the card once it’s made.

Which sites can take fixes

Each kind of site goes live on its own. Until we have tried its writes against a real account, approving a fix through it runs a dry run: Vidrys finds the page, reads it and records exactly what it would write — nothing on your site changes — and the screen says so.