Most WordPress SEO setups still treat titles like a character counter from 2014. Sixty characters. Done. Then a title full of wide capitals and long words gets cut mid-phrase in the real SERP, while a skinny title wastes space. The preview lied because it counted letters, not pixels.
The other quiet failure is schema. Plugins emit five disconnected JSON-LD blobs. Google asks for a graph: page points at author, author points at organization, breadcrumbs match the trail on screen. Loose blocks are easy to ship and easy for rich results to ignore.
This post covers two Rankify surfaces that fix those jobs: title and description templates with twenty-five variables and a pixel-accurate live preview, and a single connected @graph for Organization, WebSite, WebPage, Article, Author, plus richer Pro types. Not AI crawler policy, not 404 redirects, not ChatGPT referral dashboards.
For Yoast coexistence and AI traffic, see Rankify reads Yoast titles, then shows if ChatGPT sent traffic. For answer-engine structure, see how to tell AI answer engines using WordPress pages.
The problem: character counts and orphan schema
Titles. Google truncates by display width. WWWWW is not the same width as iiiii. A plugin that only counts characters will green-light titles that still ellipsis in the wild.
Schema. Five separate script tags that never reference each other are weaker than one @graph with @id links. Breadcrumbs that disagree with the visible trail are worse than no breadcrumbs.
Rankify is built around both: templates per post type with a preview measured in the pixel width Google cuts at, and cross-referenced structured data instead of a pile of blocks.
Title and description templates that scale
One template per post type (and taxonomy / archive where you set it). A thousand posts get a correct pattern without a thousand manual decisions.
Twenty-five variables so you can compose Primary keyword | Brand, Product - category | Store, and similar patterns without PHP.
Live Google preview that updates as you type.
Pixel-accurate length, because capital letters and wide glyphs matter.
Per-page overrides when a money page deserves a hand-written title.
A sane default pattern
- Posts:
{title} | {site_name}(or keyword-led if that is your style) - Products:
{title} | {primary_category} | {site_name} - Pages: keep human titles short; do not force blog patterns onto Pricing
Write for the snippet a stranger will click, not for stuffing every synonym into the tab title.
Descriptions
Templates help empty archives. Still rewrite meta descriptions on cornerstone URLs. Rankify’s in-browser content analysis checks focus keyword, readability, headings, links, and alt text locally as you write, with no account and no upload. Use it while you edit the override pages.
One connected schema graph
Rankify builds a single @graph where:
- The page references its author
- The author references the organization
- The breadcrumb trail matches what users see
Included building blocks cover Organization, WebSite, WebPage, Article, and Author, cross-referenced. Pro adds richer types such as Product, Recipe, Event, How-to, Course, and more (eleven rich types on the product page positioning).
WooCommerce note. Pro Product schema pulls price, stock, rating, brand, and GTIN from live store data and refreshes when the product changes. Variable products get a proper price range. Cart, checkout, and account stay out of the index.
XML sitemaps. Paginated, styled, and set to exclude anything marked noindex. Keep the sitemap honest so Google and your performance preloader see the same URL set.
Migration without a merge meltdown
Already on Yoast, Rank Math, All in One SEO, or SEOPress? Rankify can read titles, descriptions, canonicals, focus keywords, and robots settings in place. Nothing is copied, moved, or deleted. Your old plugin keeps working until you deactivate it. New edits in Rankify take over from then on. Run one SEO plugin’s output at a time so you do not emit duplicate meta tags. Rankify warns when another plugin fights over Open Graph.
Pitfalls
- Leaving two SEO plugins outputting tags. Deactivate the old one once Rankify’s preview looks right.
- Trusting character count muscle memory. Look at the pixel preview, especially with all-caps brands.
- Schema for vanity. Do not mark up FAQ blocks you did not write. Invalid or misleading rich results get ignored or worse.
- Forgetting Local SEO when you have a real shop. Pro LocalBusiness, hours, and locations exist for a reason.
- Skipping answer blocks on Q&A content. FAQ and QAPage markup from the block editor helps both rich results and AI quotability. Different article, same plugin.
Free vs Pro (honest split)
Free Rankify is already a full SEO plugin: titles and descriptions, sitemaps, schema, redirects, 404 monitor, content analysis, social tags, breadcrumbs, robots.txt, llms.txt, AI crawler control, and a 7-day crawler log.
Pro adds the rich schema library, WooCommerce and Local SEO, internal link suggestions and orphan report, auto-redirect on slug change, answer blocks and retrieval score, verified crawler identity with 90-day history, AI referral tracking, IndexNow, and role manager.
Same membership as the rest of DaftPlug Pro. Site-count tiers only on pricing.
Internal links and orphans (Pro)
Pixel-perfect titles still fail if the page is an orphan. Pro internal link suggestions and the orphan report sit next to the template work. After you lock templates, spend one pass connecting cornerstone URLs so the graph of clicks matches the graph of schema.
Social previews in the same pass
Open Graph and X cards should match the SEO title story, not fight it. Rankify warns when another plugin competes on social tags. Fix that while you are already in the SEO panel so Slack and iMessage previews do not show a different headline than Google.
Takeaway
Stop green-lighting titles with a character counter and stop shipping orphan JSON-LD. Use Rankify templates with a pixel-accurate preview, override the pages that earn money by hand, and emit one connected schema graph that matches the page humans see.