Rankavia

Author: Rankavia Editorial

  • Rankavia open beta: what works today

    Rankavia open beta: what works today

    Rankavia is in the open beta stage: the free WordPress plugins are built, the scanner is live on rankavia.com, and the hub you are reading this on runs the same plugins on every page. This post explains what you can try today and what is still being built.

    Available now

    • The free site scanner at rankavia.com, scoring any URL for search engines, answer engines, generative engines and speed.
    • Title and description templates with variables, per post type, archive, author, date, search and 404 page, with a live preview.
    • Per-page overrides for title, description, canonical, robots and social tags.
    • Open Graph and Twitter cards, head cleanup, attachment redirects and search-appearance controls.
    • Rankavia Speed’s safe defaults: emoji and legacy script removal, with page caching and lazy-loading next.

    Coming before the WordPress.org listing

    • XML sitemaps, robots.txt editor with the AI crawler policy presets, breadcrumbs and the schema graph.
    • Redirect manager with a 404 monitor.
    • Importers from Yoast, Rank Math, All in One SEO and SEOPress.
    • Answer blocks, author E-E-A-T, llms.txt, IndexNow.

    How to follow along

    Join the waitlist on rankavia.com to hear when the plugin lands in the directory, or scan your own site now and send us the report if something looks wrong. Every check in the scanner is the same check the plugin runs, so a disagreement between the two is a bug we want to know about.

  • How Google AI Overviews choose which pages to use

    How Google AI Overviews choose which pages to use

    Google AI Overviews and AI Mode do not pick pages the way the ten blue links did. They fan a question out into sub-questions, fetch candidates for each, and assemble an answer from the pages that cover the most ground credibly. The implication for a writer is simple and uncomfortable: a thin page cannot win, however well it is optimised.

    What “depth” means in practice

    Take the question your page answers and write down the five questions a careful reader would ask next. If your page answers three of them in passing and ignores two, you have found your edit. This is the “query fan-out” idea, and it is the single most useful lens for GEO work.

    Signals that read as trust

    • Outbound citations to primary sources, with real links.
    • Original numbers: your own measurements, survey, or worked example.
    • A table where a comparison is being made.
    • Semantic HTML: the article in an <article>, navigation in <nav>, so the model can discard the chrome.
    • A clear “Updated on” date that matches dateModified.

    What the GEO score checks

    Rankavia’s generative-engine score looks for exactly these things on the rendered page: sub-topic coverage against the heading structure, the presence of citations, tables and original data, semantic wrappers, and freshness. It then lists the specific gaps for the page in front of you. It will not write the missing section for you unless you ask it to draft one with your own AI key, and even then you approve every word.

  • Migrating from Yoast or Rank Math without losing anything

    Migrating from Yoast or Rank Math without losing anything

    Switching SEO plugins is mostly fear of losing settings you have forgotten you made. Rankavia’s importer reads them all, shows you the differences, and keeps a rollback for thirty days. Here is what carries over from each plugin and what changes.

    What is imported

    From Yoast, Rank Math, All in One SEO and SEOPress: per-post titles and descriptions, focus keywords, canonical URLs, robots settings, social titles, descriptions and images, redirects, schema type choices, title templates for each post type and archive, the separator, breadcrumb settings, sitemap inclusions and the default social image. Variables are translated between syntaxes; Yoast’s %%title%% becomes %title% and so on.

    What is different afterwards

    Three things. First, the Visibility Score replaces the traffic-light per-post score; the checks overlap, but ours include speed and answer-engine readability. Second, AI crawler policy is a first-class setting rather than a manual robots.txt edit. Third, speed features live in a separate plugin, Rankavia Speed, so a performance change can never take your SEO settings down with it.

    The safe order

    1. Install Rankavia alongside the old plugin; it stays silent while another SEO plugin is active.
    2. Run the importer and read the diff. Nothing is written until you confirm.
    3. Deactivate the old plugin. Do not delete it yet.
    4. Check five pages: home, a post, a page, a category, a product if you sell.
    5. Delete the old plugin after a week of normal traffic.

    Rankings do not drop because you changed plugins. They drop when a title template silently changes or a redirect goes missing, and the diff exists so neither happens unnoticed.

  • The structured data that is still worth adding

    The structured data that is still worth adding

    Structured data is worth adding when it changes how a page is shown or understood, and not otherwise. Here is the short list that still pays in 2026 and the longer list that quietly stopped.

    Still worth it

    • Organization and WebSite on the home page: who you are, your logo, your official profiles. This feeds knowledge panels and helps answer engines resolve your brand as an entity.
    • Article with author, datePublished and dateModified: the baseline every content page should carry.
    • Product with Offer, price, availability and ratings: still produces rich results and feeds shopping surfaces.
    • BreadcrumbList: cheap, and it replaces the URL in result snippets with a readable path.
    • LocalBusiness with opening hours and address: essential for anything with a physical location.

    Mostly decorative now

    • FAQPage: rich results were withdrawn for all but government and health sites. The visible Q&A still helps readers and answer engines; the markup does little.
    • HowTo: removed from results entirely.
    • Speakable: supported by almost nothing that users touch.

    How Rankavia handles it

    One connected graph per page rather than scattered blocks: Organization, WebSite, WebPage, Article and BreadcrumbList with stable identifiers linking them. You pick the page type when it differs from the default, paste custom JSON-LD when you need something unusual, and the validator tells you before publishing whether it parses. The types that stopped paying are still available, labelled as informational, so nobody mistakes them for a ranking lever.

  • Fixing Largest Contentful Paint, in the right order

    Fixing Largest Contentful Paint, in the right order

    Largest Contentful Paint is the Core Web Vital most sites fail, and on most of them the culprit is the same image: the hero at the top of the page. Here is the order of operations that fixes it without touching the design.

    1. Find the LCP element

    PageSpeed Insights names it. Nine times out of ten it is the hero image or a background image set in CSS. If it is a background image, that alone costs you, because the browser discovers it late.

    2. Stop lazy-loading it

    Lazy-loading everything is the single most common self-inflicted LCP problem. The hero must load eagerly with fetchpriority="high". Rankavia Speed excludes the LCP image from lazy-loading automatically and adds the priority hint.

    3. Preload it and size it

    A <link rel="preload"> for the hero and explicit width and height attributes on every image. The first starts the download earlier; the second stops the layout jumping, which is a different metric but the same fix.

    4. Serve a smaller file

    WebP or AVIF, properly sized for the slot. A 2,400-pixel photograph in a 1,200-pixel column is the second most common problem after lazy-loading.

    5. Get the server out of the way

    Time to first byte caps everything after it. Page caching, a CDN in front of static files, and no render-blocking CSS above the hero. Only after these should anyone look at critical CSS or JavaScript delays.

    Measure before and after with field data, not just lab scores. The plugin dashboard shows both for your key pages.

  • How to write pages that answer engines cite

    How to write pages that answer engines cite

    When an answer engine cites a page, it is usually quoting one or two sentences. Pages get cited because those sentences exist and can be found. That is a writing problem more than a markup problem, and it is fixable in an afternoon.

    State the answer first

    Under every question-shaped heading, the first sentence should be the answer in plain words. Context, caveats and examples come after. Models and people both read top-down, and both leave early.

    Use headings that are questions

    “How long does a WordPress migration take?” is a heading an engine can match to a query. “Timeline” is not. You do not need every heading to be a question, but the ones that carry the main answers should be.

    Show who wrote it and when

    A visible author with a short bio, a visible date, and matching Person and dateModified fields in the page’s structured data. Engines weigh this more than they used to, and the plugin outputs it automatically from the author profile.

    Give them something to quote

    A number, a definition, a short list of steps, a comparison table. Original material is what gets cited; a paraphrase of someone else’s page is what gets skipped. Rankavia’s answer blocks (Key takeaways, Definition, Steps, Pros and cons) exist to make this structure easy to add without touching the theme.

    What about FAQ schema and llms.txt?

    Add them if they are cheap, and do not expect them to rank you. FAQ rich results are gone for most sites, and llms.txt is a courtesy index that some crawlers read and none are obliged to. Rankavia labels both honestly in the interface for that reason.

  • Are you blocking AI crawlers without meaning to?

    Are you blocking AI crawlers without meaning to?

    Every answer engine has a crawler, and every crawler reads robots.txt. Blocking them all is a decision some publishers make deliberately. Blocking them by accident, because a plugin or a host added a rule years ago, is far more common.

    Which bots are we talking about?

    OpenAI runs GPTBot for training and OAI-SearchBot for ChatGPT search results. Anthropic runs ClaudeBot. Perplexity runs PerplexityBot. Google-Extended controls whether your content feeds Gemini, separately from ordinary Google search. Bingbot feeds both Bing and Copilot. Then there are CCBot, Applebot-Extended, Bytespider and Meta-ExternalAgent, each with their own purpose.

    Search yes, training no

    The most defensible policy for a business site is to allow the bots that send visitors and to decide separately about the ones that only train models. That means allowing OAI-SearchBot, PerplexityBot and Bingbot, and making a conscious choice about GPTBot, ClaudeBot, Google-Extended and CCBot. Rankavia ships this as a one-click preset, writes the rules into robots.txt, and shows you what each bot actually fetched in the AI bot log.

    How to check what you have today

    Open /robots.txt on your own domain and look for any User-agent block that names one of the bots above, or a blanket Disallow: /. Then check the response headers of a page for X-Robots-Tag. The free AI crawler check on rankavia.com does both and tells you, bot by bot, whether you are allowing, blocking or saying nothing.

    Saying nothing is allowing. If that is not what you intend, write it down.

  • Title tags and meta descriptions: the rules that still matter

    Title tags and meta descriptions: the rules that still matter

    Title tags are the oldest lever in SEO and still one of the few that changes click-through rates directly. The rules are short, and most sites break at least one of them.

    How long should a title be?

    Between 30 and 60 characters. Google renders titles by pixel width, not characters, so 60 is a guide rather than a wall, but past it the end gets cut on mobile. Below 30 you are usually leaving the topic unsaid. Put the specific words first and the brand last; a reader scanning results reads the beginning of the line and little else.

    Should the brand be in every title?

    Yes, at the end, separated by a consistent character. Rankavia uses templates for this so you never type the site name by hand: %title% %sep% %sitename% is the default for posts, and the separator is one setting for the whole site. When a page has an empty title the template collapses cleanly to the site name instead of leaving a dangling dash.

    Does the meta description affect rankings?

    Not directly, and Google rewrites it about half the time. It still matters because the other half is the text that persuades someone to click, and because answer engines read it as a summary of the page. Write it as a one-sentence answer of 70 to 160 characters. If you cannot summarise the page in a sentence, that is a sign about the page, not the description.

    What about duplicate titles?

    Duplicates happen on archives, paginated lists and tag pages more than on articles. Templates solve most of it: a page number variable on paginated titles, the term name on archives, the author name on author pages. The remaining duplicates show up in the site audit as a single list you can work through.

    Updated on 8 October 2026.

  • What the Visibility Score actually measures

    What the Visibility Score actually measures

    Most SEO plugins give you a score. Rankavia gives you one score with four parts, and each part answers a different question about your page: can search engines read it, can answer engines quote it, can generative engines trust it, and does it load fast enough for anyone to care.

    What the four parts measure

    Search engines covers the classics: one title of a sensible length, a meta description, a canonical URL, a single H1, robots directives that do not contradict each other, and structured data that validates. These are the checks every crawler has run for a decade, and they still decide whether a page is indexed cleanly.

    Answer engines looks at the page the way ChatGPT, Perplexity or Copilot do when they need a quotable sentence. Is the answer stated plainly near the top? Are there headings phrased as questions? Is the author identifiable? Is the date visible? None of this is magic; it is the difference between a page that can be cited and one that has to be paraphrased.

    Generative engines is about depth and trust: does the page cover the sub-topics a reader would ask next, does it cite sources, does it carry original data or examples, and is the HTML semantic enough that a model can tell the article from the sidebar.

    Speed is Core Web Vitals, measured the way Google measures them. A slow page loses the visitor before any of the above matters.

    Why one number

    Because the people who own sites are not SEO specialists, and the four areas pull against each other if you optimise them separately. A page stuffed with schema can still be unreadable to an answer engine. A fast page can have no title. The Visibility Score forces the trade-offs into view and tells you which single change moves the number most.

    The score is a measure of what we can see from the outside. It does not promise rankings, and no tool honestly can. What it does promise is that every red item on the list is something you can fix today, and that the free scanner on rankavia.com and the plugin dashboard will agree with each other about it.