| 开发者 | avakodeforge |
|---|---|
| 更新时间 | 2026年11月9日 12:04 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
rankforge to /wp-content/plugins/, or install via Plugins → Add New.No. While another SEO plugin is active, Rank Forge takes that plugin's duplicate meta description, robots, social and schema tags off the page and prints its own; the other plugin's search engine verification codes stay. Use Rank Forge → Migration when you are ready to bring its data over.
Yes. The migration tool imports titles, descriptions, focus keywords, canonical URLs, robots settings and social fields from Yoast SEO, Rank Math, AIOSEO and SEOPress, and the SEOPress importer also imports redirects. It reads the database directly, so the other plugin does not have to be running.
Yes. It adds Product schema to WooCommerce product pages. The Pro add-on also audits your most recent products for titles, descriptions, focus keywords and alt text.
This plugin is the free version. It includes the SEO score, SERP preview, focus keyword analysis, XML sitemap, robots.txt editor, schema markup with the visual Schema Builder, redirects with a 404 log, broken-link scanner, image SEO, local business schema and video SEO. AI features, Google Search Console, site audit, A/B testing and automatic internal links are in the separate Rank Forge Pro add-on.
No. The free plugin needs no account and no API key. The AI features belong to the Pro add-on and run through the Avakode service on Forge credits, so there is no key of your own to paste.
No. The score is deterministic: keyword density, readability, internal links, image alt text and similar checks. AI is used only for generation actions, such as meta text, schema or content expansion, when you click the AI button of the Pro add-on.
In a custom table, wp_rankforge_redirects, not in wp_options. This avoids the autoload bloat that slows down your server response time.
http:/other.example, http:other.example, // with no host, /\other.example, or an address with a tab or a line break inside. A target written as //other.example/page is an address on another host, so it needs "Allow redirect to external domain". Rules whose target is mailto:, tel: 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, the address /blog-post is no longer taken for an address inside the folder.{{excerpt}} 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.<title> is escaped the same way as the meta title tag (Yoast still gets the raw text).sameAs and openingHours of the Local Business markup are lists without empty items.u041f…, 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.fb:app_id, fb:admins, twitter:site, twitter:creator, og:locale and article:* stay).#name form, and the ones Rank Forge cannot fill are dropped with the text between them kept._seoforge_ row no longer doubles a live _rankforge_ 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.{{page}} 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%% and the Rank Math %page% into {{page}}._ and -. The live preview in Title Templates does the same.{{page}} or {{siteName}} is printed as typed, and a separator with spaces of its own no longer doubles them before "Page N".