Needs Rank Forge Pro 1.2.5 or newer if you run the add-on, as before. Broken Links now scans every published post in the background and once a night, and a site set to discourage search engines no longer has a sitemap. Redirect targets that a browser reads as another site are refused.<\/p>","1.2.10":"
Needs Rank Forge Pro 1.2.5 or newer if you run the add-on, as before. Category, tag and custom taxonomy archives now use the title and description templates imported from Yoast SEO or Rank Math, so their titles can change.<\/p>","1.2.9":"
Needs Rank Forge Pro 1.2.5 or newer if you run the add-on, as before. With Pro 1.2.13 or newer, Performance and Content Decay now say when the add-on has no licence for Search Console, instead of asking you to connect Google.<\/p>","1.2.8":"
Needs Rank Forge Pro 1.2.5 or newer if you run the add-on, as before. With Pro 1.2.13, Content Decay and Performance say when Search Console data is not being loaded. A PHP 8.1 deprecation notice no longer reaches debug.log.<\/p>","1.2.7":"
Needs Rank Forge Pro 1.2.5 or newer if you run the add-on, as before. The site name is no longer printed as a product's brand: a shop that has not set a brand ends up without the brand property. Set the brand on the product or under Settings, Search Appearance.<\/p>","1.2.6":"
Needs Rank Forge Pro 1.2.5 or newer if you run the add-on, as before. Fixes: a Thumbnail URL and Description typed in the Video SEO box are kept when the Video URL is empty, and a redirect with an unsupported type shows an error instead of being saved as a 301.<\/p>","1.2.5":"
Needs Rank Forge Pro 1.2.5 or newer if you run the add-on, as before. Fixes: Auto-Link no longer says "Linked!" when it added nothing, 410 redirect rules answer 410 Gone, saving Settings keeps the settings it has no field for, and the Veterinarian and Locksmith schema types are real ones.<\/p>","1.2.4":"
Needs Rank Forge Pro 1.2.5 or newer if you run the add-on, as before.<\/p>","1.2.3":"
The Dashboard screen shows its header and styles again. Deleting the plugin cleans up on every site of a network. If you run Rank Forge Pro, it must be 1.2.5 or newer.<\/p>","1.2.2":"
The Google Search Console card in Settings, Integrations points to the add-on's own screen instead of drawing a sign-in button. robots.txt is written only where WordPress can write files directly. If you run Rank Forge Pro, it must be 1.2.5 or newer.<\/p>","1.2.1":"
A shortcode that fails inside the FAQ, HowTo or Recipe markup can now be reported to your own log through a new action. If you run Rank Forge Pro, it must be 1.2.5 or newer.<\/p>","1.2.0":"
The Dashboard's first card now runs the site-wide analysis and names your weakest post, and the AI Search Readiness report lists its strengths and suggestions. If you run Rank Forge Pro, it must be 1.2.5 or newer.<\/p>","1.1.13":"
Deleting the plugin leaves the job queue shared by the Forge plugins alone while another one is still installed. If you run Rank Forge Pro, it must be 1.2.5 or newer.<\/p>","1.1.12":"
Needs Rank Forge Pro 1.2.5 or newer if you run the add-on: the licence screen moved into it, and an older add-on stays switched off until it is updated. The editor shows no locked AI buttons.<\/p>","1.1.11":"
Still needs Rank Forge Pro 1.2.0 or newer. The PRO badges follow whether the add-on is installed, and the add-on's screens check for it before they open.<\/p>","1.1.10":"
Needs Rank Forge Pro 1.2.0 or newer: an older add-on is switched off whole rather than left running on an entitlement this version cannot honour.<\/p>","1.1.9":"
Fixes a fatal error on the post editor and three other screens for sites whose Pro add-on is inactive or older than 1.2.0. Needs Rank Forge Pro 1.2.0 or newer: an older add-on is switched off whole rather than left running on an entitlement this version cannot honour.<\/p>","1.0.32":"
Adds a Support menu and dashboard Pro tips.<\/p>","1.0.29":"
Optional title "ideas" no longer counted as issues, clearer Google Indexing setup, and WordPress.org compliance fixes.<\/p>","1.0.25":"
Licensing and WordPress.org compliance improvements.<\/p>","1.0.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3748975,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3748975,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3748975,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3748975,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.10","1.1.11","1.1.12","1.1.13","1.1.6","1.1.7","1.1.8","1.1.9","1.2.0","1.2.1","1.2.10","1.2.2","1.2.3","1.2.5","1.2.6","1.2.7","1.2.8","1.2.9","1.3.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3720770,"resolution":"1","location":"assets","locale":"","width":1280,"height":1000},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3720770,"resolution":"2","location":"assets","locale":"","width":1280,"height":1000},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3720770,"resolution":"3","location":"assets","locale":"","width":1280,"height":1000},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3720770,"resolution":"4","location":"assets","locale":"","width":1280,"height":1000},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3720770,"resolution":"5","location":"assets","locale":"","width":1280,"height":1000},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3720770,"resolution":"6","location":"assets","locale":"","width":1280,"height":1000}},"screenshots":{"1":"The SEO box in the post editor: a score out of 100, the focus keyword, length meters for the SEO title and meta description, and a Google preview.","2":"The checks behind the score: the issues that cost points and optional ideas, each in plain words.","3":"Schema markup for the post, detected as an Article, with every field filled from the content and editable.","4":"The dashboard: what to fix first, the score across all posts and the most common issues.","5":"Redirects with their hit counts, one created automatically when a post's slug changed, and the missing pages visitors asked for.","6":"The XML sitemap search engines read, with a preview people can read too."}},"plugin_section":[262246],"plugin_tags":[2988,1117,186,240424,1557],"plugin_category":[55,57],"plugin_contributors":[273812],"plugin_business_model":[],"class_list":["post-351728","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-meta-tags","plugin_tags-schema","plugin_tags-seo","plugin_tags-serp-preview","plugin_tags-sitemap","plugin_category-seo-and-marketing","plugin_category-taxonomy","plugin_contributors-avakodeforge","plugin_committers-avakodeforge"],"banners":{"banner":"https:\/\/ps.w.org\/rank-forge\/assets\/banner-772x250.png?rev=3748975","banner_2x":"https:\/\/ps.w.org\/rank-forge\/assets\/banner-1544x500.png?rev=3748975","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/rank-forge\/assets\/icon-128x128.png?rev=3748975","icon_2x":"https:\/\/ps.w.org\/rank-forge\/assets\/icon-256x256.png?rev=3748975","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/rank-forge\/assets\/screenshot-1.png?rev=3720770","caption":"The SEO box in the post editor: a score out of 100, the focus keyword, length meters for the SEO title and meta description, and a Google preview."},{"src":"https:\/\/ps.w.org\/rank-forge\/assets\/screenshot-2.png?rev=3720770","caption":"The checks behind the score: the issues that cost points and optional ideas, each in plain words."},{"src":"https:\/\/ps.w.org\/rank-forge\/assets\/screenshot-3.png?rev=3720770","caption":"Schema markup for the post, detected as an Article, with every field filled from the content and editable."},{"src":"https:\/\/ps.w.org\/rank-forge\/assets\/screenshot-4.png?rev=3720770","caption":"The dashboard: what to fix first, the score across all posts and the most common issues."},{"src":"https:\/\/ps.w.org\/rank-forge\/assets\/screenshot-5.png?rev=3720770","caption":"Redirects with their hit counts, one created automatically when a post's slug changed, and the missing pages visitors asked for."},{"src":"https:\/\/ps.w.org\/rank-forge\/assets\/screenshot-6.png?rev=3720770","caption":"The XML sitemap search engines read, with a preview people can read too."}],"raw_content":"\n
Rank Forge<\/strong> is a modern SEO plugin built around a single insight: an SEO score is only useful if it tells you exactly what to do next. The post-edit metabox gives you a 0-100 SEO score, a SERP preview, focus-keyword analysis, and an editable meta title \/ description \/ schema \u2014 all from one screen, with no account or API key required.<\/p>\n\n Everything in the Free plugin happens on your own site: schema markup, XML sitemap, robots.txt, the redirect + 404 manager, image SEO (auto alt text), local business schema, and video schema. The only requests it makes are the two listed under External services: the Broken Links scan, when you start it, and the check of your own site's robots.txt. The optional Pro add-on<\/strong> layers AI on top \u2014 one-click AI meta generation, content optimization, and schema detection \u2014 plus Google Search Console, Site Audit, A\/B testing and auto internal links.<\/p>\n\n Pro is a separate add-on plugin, distributed from https:\/\/rankforgewp.com and not\nincluded in this download. Everything listed above is part of this plugin and\nworks without it.<\/p>\n\n Part of the Forge Suite<\/strong>: twelve WordPress and WooCommerce plugins by Avakode, including Lang Forge, Form Forge and Field Forge.<\/p>\n\n Rank Forge can make outbound HTTP requests. Nothing is sent until you use the feature that sends it: activating the plugin does not contact any server and does not schedule anything that would. This is the whole list: the plugin's code makes no other request. Each one is an ordinary WordPress HTTP request, so the server it reaches sees the network address it came from.<\/p>\n\n Search Console, Analytics and Indexing, and the AI features, belong to the separate Rank Forge Pro add-on, which describes the services it uses in its own documentation. This plugin has no analytics, no telemetry and no licensing calls of its own.<\/p>\n\n\n No. Rank Forge detects the active SEO plugin and suppresses its own meta output until you fully migrate. Use Rank Forge \u2192 Migration<\/strong> when ready.<\/p><\/dd>\n The score itself is deterministic (keyword density, readability, internal links, image alt, etc.). AI is only used for generation actions (meta, schema, content expansion) when you click \"Generate with AI\".<\/p><\/dd>\n In a custom table (Free<\/h4>\n\n
\n
Rank Forge Pro<\/h4>\n\n
\n
External services<\/h3>\n\n
\n
\/robots.txt<\/code> at your own site's address with a plain GET, no body and no credentials, to show what visitors and crawlers receive; the answer is kept for 60 seconds. The request goes to your own site, carries WordPress's standard user-agent (which names your site's address), and nothing is sent to any other server.<\/li>\n<\/ul>\n\n\n
rankforge<\/code> to \/wp-content\/plugins\/<\/code>, or install via Plugins \u2192 Add New.<\/li>\n\n
Will Rank Forge conflict with Yoast or Rank Math?<\/h3><\/dt>\n
Does the SEO score use AI?<\/h3><\/dt>\n
How are redirects stored?<\/h3><\/dt>\n
wp_rankforge_redirects<\/code>) \u2014 not in wp_options<\/code> like some plugins. This avoids the autoload-bloat that hurts your TTFB.<\/p><\/dd>\n\n<\/dl>\n\n\n1.3.0<\/h4>\n\n
\n
http:\/other.example<\/code>, http:other.example<\/code>, \/\/<\/code> with no host, \/\\other.example<\/code>, or an address with a tab or a line break inside. A target written as \/\/other.example\/page<\/code> is an address on another host, so it needs \"Allow redirect to external domain\". Rules whose target is mailto:<\/code>, tel:<\/code> or another address that is not a web address no longer fire, and the Redirects list marks them. On a site in a sub-folder such as \/blog<\/code>, the address \/blog-post<\/code> is no longer taken for an address inside the folder.<\/li>\n{{excerpt}}<\/code> variable, the automatic description and the descriptions in the JSON-LD markup take the post text without its shortcodes instead of printing them as literal text, and a post that is one shortcode pair from start to end gets no description tag.<\/li>\n<title><\/code> is escaped the same way as the meta title tag (Yoast still gets the raw text).<\/li>\nsameAs<\/code> and openingHours<\/code> of the Local Business markup are lists without empty items.<\/li>\nu041f\u2026<\/code>, and quotes and backslashes were lost. The data is now saved the way WordPress expects it. Entries saved before stay as they are: open the post, type the text in the form again and save to repair it.<\/li>\nfb:app_id<\/code>, fb:admins<\/code>, twitter:site<\/code>, twitter:creator<\/code>, og:locale<\/code> and article:*<\/code> stay).<\/li>\n#name<\/code> form, and the ones Rank Forge cannot fill are dropped with the text between them kept.<\/li>\n_seoforge_<\/code> row no longer doubles a live _rankforge_<\/code> field, and a one-time repair merges the rows that were doubled. It works through the posts in small windows under a lock and marks itself done only after a clean pass over all of them.<\/li>\n1.2.10<\/h4>\n\n
\n
{{page}}<\/code> variable (\"Page 2\", from page 2 on) can stand anywhere in a title template; a term archive title without it gets the separator and \"Page N\" at its end from page 2 on. The import turns the Yoast %%page%%<\/code> and the Rank Math %page%<\/code> into {{page}}<\/code>.<\/li>\n_<\/code> and -<\/code>. The live preview in Title Templates does the same.<\/li>\n{{page}}<\/code> or {{siteName}}<\/code> is printed as typed, and a separator with spaces of its own no longer doubles them before \"Page N\".<\/li>\n1.2.9<\/h4>\n\n
\n
1.2.8<\/h4>\n\n
\n
1.2.7<\/h4>\n\n
\n
1.2.6<\/h4>\n\n
\n
1.2.5<\/h4>\n\n
\n
1.2.4<\/h4>\n\n
\n
1.2.3<\/h4>\n\n
\n
1.2.2<\/h4>\n\n
\n
1.2.1<\/h4>\n\n
\n
rankforge_schema_shortcode_failed<\/code> now tells your site, with what was thrown, the post and the fragment. Nothing is written to a log by default: hook your own logging onto the action if you want to know. What a handler prints stays out of the page head, and an error it throws goes no further.<\/li>\n<\/ul>\n\n1.2.0<\/h4>\n\n
\n
<lastmod><\/code> in UTC. On a site set to a time zone behind UTC the dates ran ahead of the real time, and search engines can ignore a date in the future. A post without a valid modified date has no <lastmod><\/code>.<\/li>\nrankforge_schema_render_shortcodes<\/code> filter turns the rendering off.<\/li>\nrankforge_canonical_url<\/code>: another plugin can change a post's custom canonical URL, or withdraw it by returning an empty string, in which case Rank Forge prints no canonical tag for that post.<\/li>\n<\/ul>\n\n1.1.13<\/h4>\n\n
\n
1.1.12<\/h4>\n\n
\n
1.1.11<\/h4>\n\n
\n
1.1.10<\/h4>\n\n
\n
1.1.9<\/h4>\n\n
\n
1.1.8<\/h4>\n\n
\n
1.1.7<\/h4>\n\n
\n
1.1.6<\/h4>\n\n
\n
1.1.5<\/h4>\n\n
\n
1.1.4<\/h4>\n\n
\n
1.1.3<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.40<\/h4>\n\n
\n