Technical SEO issues: Every issue, grouped by cause. Ranked by what matters.

Issues is correctness and Opportunities is leverage. A check fails whether or not anyone searches for the page, so Issues lists all of it. A finding becomes an Opportunity only when a market signal quantifies the upside, so Opportunities shows the subset worth money. Three signals overlap, and a row on either side carries a marker pointing at the other.

A deterministic function of the check and the finding's own evidence. A meta description four characters over the 160 target is safe to skip; the same check at 230 is worth fixing. No model grades anything here, and the safe-to-skip band starts collapsed because a large site produces thousands of trivial findings.

Across the 85 check types, Verand drafts titles and meta descriptions in bulk, and many others come with a drafted fix you can apply or copy: broken links, alt text, page schema, canonical and social tags, a stray noindex, link labels, the main heading, duplicate titles, banned-claim rewording and a missing disclaimer. An applied fix shows as fixed only once the live page confirms it. It also writes llms.txt, robots.txt and sitemap.xml from your own crawled pages, drafts an editorial standards page and an AI instructions page, and can unblock AI crawlers through the Connector. Findings without a drafted fix get the prescription and the list of pages; author-schema findings link to Author Bio Pro, which renders them.

Only what you approve. A drafted fix sits in Verand until you press Apply, and Apply changes only the page you chose. On WordPress, and on GitHub sites whether they serve plain HTML or build from Markdown, that covers the title and meta description, links, alt text, citations, page schema and the year rollover. On WordPress, a meta description or a separate SEO title needs the free Verand Connector, unless the site runs Rank Math. On a git site the change is committed to your repo and shows as fixed once your site rebuilds and the live page confirms it. If Verand can't tell how your repo builds its pages, or no site is connected, you copy the change in yourself.

Mark them as intended. Pages alike by design, like one page per place or product, can be marked as a group, or as a whole section such as /locations/ so new pages under it are covered too. They leave Issues and stop costing score, and Undo sits in the Marked as intended list. When two pages shouldn't compete, Plan the merge keeps the one with the most Google clicks in Search Console, and Keep this instead overrules it; without Search Console it asks you to pick rather than guess. The plan says what to move into the kept page, which redirects to add and which links to update, and Suggest angles gives each page its own angle instead. Both are advice: nothing changes on your site until you make the edits.

Yes, as drafts you finish. The crawl checks for both, and each finding drafts the page from your Brand Hub: your authors, reviewer and sources for editorial standards, and your positioning, products and the facts from AI answers you've confirmed or corrected for AI instructions. It says only what those hold and leaves the rest in [brackets] for you. Edit it in place, then create it as a WordPress draft page or a GitHub pull request; the pull request waits until no bracket is left, and both go through your compliance rules first. Without a connected site you copy or download it. Once it's live, Re-check now or the next crawl finds it and closes the finding.

Exports unlock when your plan starts. Viewing is never gated, on any plan or during the trial, and the articles you write in Verand export on any plan, because they are yours. The sheet is one row per issue type with its category, severity, verdict, page count, whether a fix or an AI draft is available, and the guidance.

The deep crawl runs on the 1st and the 15th on every plan, and Re-run audit is there when you want it sooner. Pages whose content hash has not moved are not re-read by the deeper checks, so a re-crawl costs close to nothing on a site that did not change.