Title: PublishRank
Author: umarjaum
Published: November 5, 2026
Last modified: November 6, 2026
---
Search plugins
# PublishRank
By [umarjaum](https://profiles.wordpress.org/umarjaum/)
[Download](https://downloads.wordpress.org/plugin/publishrank.2.9.76.zip)
* [Details](https://wordpress.org/plugins/publishrank/#description)
* [Reviews](https://wordpress.org/plugins/publishrank/#reviews)
* [Installation](https://wordpress.org/plugins/publishrank/#installation)
* [Development](https://wordpress.org/plugins/publishrank/#developers)
[Support](https://wordpress.org/support/plugin/publishrank/)
## Description
PublishRank is a free, open-source WordPress SEO plugin for site owners, bloggers,
news publishers, newspapers, magazines and editorial teams. It brings core technical
SEO workflows into one publisher-focused plugin and can be evaluated as an alternative
to Yoast SEO, Rank Math and other WordPress SEO plugins. Compare the feature set
with your current setup before switching; features and workflows are not identical
across plugins.
Copyright and project rights: Muhammad Umar Jabbar.
Features include:
* SEO titles, descriptions, canonicals, robots directives, Open Graph and X/Twitter
metadata.
* Connected JSON-LD schema for organizations, people, webpages, articles, breadcrumbs
and supported media/content types.
* XML sitemaps for posts, pages, taxonomies, authors, images and videos, including
a Google News sitemap.
* Redirect management and a privacy-conscious local 404 monitor with normalized
paths, grouped browser/mobile/crawler hits, referrer paths without query strings,
noise suppression for assets and infrastructure probes, throttled and locked
bounded writes, 90-day retention, searchable/sortable review, clearable logs,
and same-site redirect creation.
* Per-article author schema overrides for author name, job title and image, plus
selectable Article, NewsArticle and BlogPosting types.
* Global and per-content robots directives, including index/noindex and follow/
nofollow controls, plus configurable robots.txt rules.
* Robots.txt controls, hreflang support and breadcrumbs.
* IndexNow notifications and manual URL submission (optional; sends eligible public
URLs to the IndexNow service when enabled).
* Configurable llms.txt and optional llms-full.txt resources, with a public paginated
schema-discovery endpoint linked from llms.txt.
* Editorial SEO analysis, internal-link recommendations, sitemap diagnostics and
WP-CLI commands.
* Publisher Toolkit with a read-only pre-publication checklist for drafts, pending
and scheduled stories; permission-aware bulk SEO metadata editing; role-based
access; and optional image alt-text assistance that preserves existing descriptions.
* Optional built-in WP Hide Login module with a custom login endpoint, configurable
slug, administration URL rewriting where Apache rules are available, and 404
protection for direct default paths.
* Always-on technical source provenance markers in page source; they do not add
a promotional link or visible footer credit.
PublishRank does not guarantee rankings, crawling, indexing, traffic, or inclusion
in Google News. IndexNow is not supported by Google.
### Source code
PublishRank includes reviewable PHP, JavaScript and CSS source. The maintained source
repository is [github.com/Umarjaum/PublishRank](https://github.com/Umarjaum/PublishRank).
First-party runtime assets in `assets/` are shipped unminified and human-readable,
with corresponding first-party sources in `src/assets/`. Font Awesome Free 7.3.1
is bundled locally under `assets/vendor/fontawesome-free-7.3.1/` with its upstream
license. There is no build step or third-party asset CDN request.
### Documentation
* In WordPress: **PublishRank Documentation & Help** explains titles, variables,
output controls, breadcrumbs, sitemaps, schema, robots, redirects, the robust
404 Monitor, IndexNow, Baidu, diagnostics, the admin menu and toolbar, the sitemap
browser view, versions and troubleshooting.
* In the package: `docs/features/FEATURES.md` lists every dashboard feature and
Technical Health check provided through version 2.9.110. The `docs/` folder also
contains guides for sitemaps, branding, admin navigation, the 404 Monitor, troubleshooting,
versioning and a WordPress 7.1.3 compatibility checklist.
* Online: [publishrankseo.vercel.app](https://publishrankseo.vercel.app/).
### Privacy
PublishRank does not include visitor analytics or send publisher content to PublishRank.
Core metadata and schema are generated locally. The technical source marker does
not contain an external link. Optional integrations below make requests only when
configured or explicitly enabled; remote services and OAuth providers may receive
the originating server or browser IP address and standard connection metadata. Review
the relevant provider policies and your own privacy obligations before enabling
an integration.
### Terms and Conditions
PublishRank is provided under the GPLv2-or-later license. The plugin does not guarantee
rankings, crawling, indexing, traffic, or inclusion in Google News. Technical provenance
markers are always present in public HTML source.
### External Services
**Google Search Console (optional, your own Google OAuth client).** Nothing is sent
to Google until an administrator saves their own Google OAuth client ID and secret
on the Search Console screen and selects **Sign in with Google**. The administrator’s
browser is then sent to Google’s OAuth page (`accounts.google.com`) and returns
to this site’s callback URL; the authorization code is exchanged directly between
this WordPress server and Google (`oauth2.googleapis.com`) using PKCE. PublishRank
requests only the read-only `webmasters.readonly` scope. The client secret and the
refresh token are stored encrypted with WordPress salts; no PublishRank-operated
server is involved and no Google data is sent to PublishRank. On connection, then
hourly (WP-Cron) and when an administrator clicks Refresh, the server asks the Google
Search Console API (`www.googleapis.com`) for the verified property list and sends
the selected property, date ranges and search type to retrieve daily, hourly, query,
page, Discover and Google News totals. A URL Inspection action also sends the entered
public page URL, property and WordPress locale. Returned metrics are cached locally.**
Disconnect** asks Google to revoke the grant (`oauth2.googleapis.com/revoke`) and
deletes the stored credentials and cached data. Google may also be opened in the
administrator’s browser for the optional Rich Results Test, which receives the public
URL the administrator chose to test. Google policies: [Google API Services User Data Policy](https://developers.google.com/terms/api-services-user-data-policy),
[Google APIs Terms](https://developers.google.com/terms), and [Google Privacy Policy](https://policies.google.com/privacy).
PublishRank’s use of information received from Google APIs adheres to the Google
API Services User Data Policy, including the Limited Use requirements.
**IndexNow (optional).** When enabled, eligible public URLs are submitted after
supported publish/update/delete events, manual submission, or a retry. The request
to `https://api.indexnow.org/indexnow/` includes the site’s host, IndexNow key,
public key-location URL and submitted URL list. The plugin keeps a bounded local
submission history including URLs and response statuses. Acceptance is not proof
of crawling or indexing, and Google does not participate in IndexNow. The official
[IndexNow Terms of Service](https://www.indexnow.org/terms) identify Yandex, Seznam
and Microsoft as sponsors. See their [Yandex Privacy Policy](https://yandex.com/legal/privacy/),
[Seznam Privacy Policy](https://o-seznam.cz/ochrana-udaju/) and [Microsoft Privacy Statement](https://privacy.microsoft.com/en-us/privacystatement).
**Baidu Search Resource Platform submission (optional).** An administrator can submit
up to 2,000 same-host public URLs manually, or explicitly enable automatic submission
for newly published eligible posts. The request is sent over HTTPS to the Baidu
endpoint configured by the publisher and includes the submitted URL list; the endpoint
URL itself contains the publisher’s Baidu site identifier and token. The endpoint
is encrypted in the WordPress database; Baidu receives the endpoint credentials
and URLs to process the request. A bounded local history stores response counts/
status, not the submitted URLs or response body. A submission is not an indexing
guarantee. See the [Baidu Search Resource Platform Agreement](https://ziyuan.baidu.com/college/articleinfo?id=1613),
[Baidu Privacy Protection Statement](https://www.baidu.com/duty/yinsiquan.html),
and [Baidu Disclaimer](https://www.baidu.com/duty/index.html).
**Publisher diagnostics (optional, administrator-triggered).** The live frontend
scan requests the site’s own homepage, latest article, sitemap index and up to ten
same-origin child sitemaps from the site’s server and analyzes the returned HTML/
XML locally. It does not follow HTTP redirects, and sitemap child URLs on another
origin are not requested. The IndexNow key check requests the site’s own public
key file. Publisher Link Intelligence analyzes locally available site data. Only
when an administrator ticks **Also check external links** and starts a scan, the
site’s server sends HEAD/GET requests to the external URLs already linked in the
site’s own content to read their HTTP status; nothing else is sent and no data is
shared with PublishRank.
**Traffic Guard (optional, local-only).** When enabled, validated request IPs and
configured IP/CIDR and country rules are compared locally. The plugin reads `CF-
Connecting-IP`, `X-Forwarded-For`, or `CF-IPCountry` only when the direct network
peer is inside an administrator-configured trusted-proxy CIDR. It makes no GeoIP
API requests, stores no per-visitor IP address, and sends no Traffic Guard data
to PublishRank or another service. Country rules require a trusted proxy that supplies
a valid country header; missing or invalid country data is allowed through. Country
geolocation is approximate, and this feature is not a WAF or DDoS defense. Administrator
requests and key WordPress recovery, API, feed, robots, and sitemap routes are exempt.
When a request would be blocked and its User-Agent claims to be a major search-engine
crawler, the server performs a reverse DNS lookup of the visiting IP and a forward
lookup of the returned host name to confirm it (the verdict is cached under a salted
hash, not the IP). These are DNS lookups made by your server, not HTTP requests,
and no data is sent to PublishRank.
Other website links in the administration interface (including the Schema.org vocabulary
and links to provider documentation) are ordinary references, not background API
integrations. PublishRank’s source-provenance markers are technical metadata only;
the plugin does not insert a visible footer credit or promotional link.
### PublishRank Newsroom
PublishRank includes a built-in editorial newsroom for story pitches and assignments,
configurable workflow stages, reporter/editor assignments, planning board, calendar,
private notes and discussion, attachments, audit history, CSV export, notifications,
and publishing handoff to WordPress drafts. The module uses dedicated newsroom capabilities
and retains newsroom records and settings when updated. Attachments are stored outside
the public document root when the server provides a writable private directory;
legacy uploads are migrated on an authorized admin request. New uploads are blocked
if private storage cannot be established. Assignment, stage, overdue-reminder, and
discussion alerts appear in a dismissible wp-admin pop-up and the Newsroom notification
inbox; users can manage email, in-app, and pop-up preferences under Newsroom My
Notifications. Alerts poll while logged into wp-admin and do not request browser
notification permission.
## Screenshots
[⌊Real-time SEO analysis with score and checklist inside the post editor.⌉⌊Real-
time SEO analysis with score and checklist inside the post editor.⌉[
Real-time SEO analysis with score and checklist inside the post editor.
[⌊SEO overview dashboard with ranking trend, indexed posts and keyword positions.⌉⌊
SEO overview dashboard with ranking trend, indexed posts and keyword positions.⌉[
SEO overview dashboard with ranking trend, indexed posts and keyword positions.
[⌊Search result preview with SEO title and meta description length guidance.⌉⌊Search
result preview with SEO title and meta description length guidance.⌉[
Search result preview with SEO title and meta description length guidance.
[⌊SEO Modules: XML sitemap, schema markup, redirects, social previews and internal
links.⌉⌊SEO Modules: XML sitemap, schema markup, redirects, social previews and
internal links.⌉[
SEO Modules: XML sitemap, schema markup, redirects, social previews and internal
links.
## Blocks
This plugin provides 1 block.
* PublishRank Breadcrumbs
## Installation
1. Upload the `publishrank` folder to `/wp-content/plugins/`, or install the ZIP through**
Plugins Add New Upload Plugin**.
2. Activate **PublishRank** from the Plugins screen.
3. Open **PublishRank** in the WordPress dashboard and complete the onboarding steps.
4. Review metadata ownership, schema, sitemap and robots settings before using the
plugin on a production site.
5. Submit the sitemap index in your search engine webmaster tools when ready.
## FAQ
### Does PublishRank add anything to my page source?
Technical HTML-source provenance markers are always enabled on public HTML pages
and cannot be disabled in settings. Source markers are not added to feeds, REST/
AJAX responses or sitemaps. Separately, PublishRank displays a small branded link
in the WordPress admin footer.
### Which articles appear in the News sitemap?
Published, public, indexable articles from the configured post types whose original
publish time is inside the publication window (48 hours by default). Drafts, scheduled,
private and password-protected posts, noindex posts and posts you excluded are left
out. An empty sitemap is valid.
### How do I mark a live blog?
Edit the post, open the Schema box, choose “Live Blog Post” as the schema type,
and add timestamped updates in the Live coverage panel. Ordinary posts are never
marked up as live blogs automatically.
### Which title and description variables are supported?
The same fifteen variables work in global title templates, per-post SEO titles and
per-post meta descriptions: %%title%%, %%sitename%%, %%site_description%%, %%category%%,%%
primary_category%%, %%author%%, %%date%%, %%modified%%, %%excerpt%%, %%sep%%, %%
page%%, %%id%%, %%permalink%%, %%focus_keyword%% and %%focuskw%%. Unknown variables
are removed.
### Can I turn off schema, metadata or breadcrumbs separately?
Yes. Output controls (Settings) switch metadata, the JSON-LD graph, the Organization/
WebSite entities, the visible breadcrumb trail and BreadcrumbList data independently.
All are enabled on new installs; existing choices are kept on upgrade. PublishRank
only changes its own output: a logo, title, breadcrumbs or meta tags hard-coded
by your theme or another plugin are not rewritten. Choose “Structured data only”
breadcrumb placement if your theme prints its own trail.
### Known limitations
A classic theme that hard-codes a
### What does the XML sitemap page in my browser show?
A readable view of the same sitemap search engines fetch as plain XML: totals, a
content showcase bar with each type’s share, one card per content type, and URL
tables with filtering for child sitemaps. Use View raw XML to see exactly what crawlers
receive. The view never changes the XML.
### How does the 404 Monitor work?
Enable **Record a capped rolling 404 log** in **PublishRank Settings**, then review
entries at **PublishRank 404 Monitor**. The monitor aggregates normalized paths
by browser, mobile or crawler category, records hit counts and first/last seen times,
and keeps only the latest useful referrer path without storing IP addresses, cookies,
request bodies or full query strings. It ignores admin, AJAX, cron, REST, non-GET/
HEAD, common static-asset and infrastructure-probe requests. The log is rate-limited,
protected against concurrent write loss, retained for 90 days and capped at 500
entries. Administrators can search paths, filter visitor categories, sort by hits
or recency, dismiss entries, clear the log, or create validated same-site redirects.
It is a bounded diagnostic aid, not a complete access log, analytics system, WAF
or DDoS defense.
### Where is the complete feature list?
The package guide `docs/features/FEATURES.md` is the complete dashboard inventory
through version 2.9.110. It includes every card under Search & discovery, Content&
publishing, Measure & maintain, and Settings & help, plus every Technical Health
check: Schema studio, Sitemap health, IndexNow, Search Console, Search engines,
Google Preferred Sources, Robots.txt, Crawl optimization, Breadcrumbs, Site verification,
AI & llms.txt, Schema Aggregator, SEO score, SEO Overrides, Google Discover image,
Author expertise, Local SEO, Image optimizer, Publisher toolkit, Newsroom, Planning
board, Newsroom calendar, Newsroom activity, My notifications, Newsroom configuration,
Newsroom roles, Internal links, Link intelligence, Publisher analytics, Insights,
Redirects, 404 monitor, Traffic Guard, WP Hide Login, Configuration history, Diagnostics,
Setup wizard, Settings, Titles & Meta, Import / Export, Documentation & help, SEO
plugin conflicts, Search engine visibility, Pretty permalinks, HTTPS, News sitemap,
Structured data coverage, Publisher logo, Default social image, Robots.txt and JNews
compatibility.
### Which logo does PublishRank use?
One file, `assets/images/publishrank-brand-mark.png`, shown in the admin sidebar,
toolbar, screen headers, setup wizard and sitemap view. No SVG or alternate icon
files are packaged.
### Why does the PublishRank admin dropdown have no custom background?
It uses WordPress’s native submenu colours so it matches every admin colour scheme.
### Is PublishRank free?
Yes. PublishRank is released under the GPLv2-or-later license. The plugin does not
require a paid AI API key for its core functionality. Optional integrations such
as IndexNow require an administrator to enable them.
### What happens when I activate PublishRank?
On first activation, an administrator sees a one-time PublishRank News prompt with**
Enable live News**, **No thanks — keep News off**, and **Not now** options. Enabling
the feed is the only choice that permits a News request. Declining or dismissing
leaves News off; you can enable it later at **PublishRank News**. If an administrator
had already enabled News, that saved choice is preserved.
### Is PublishRank an alternative to Yoast SEO or Rank Math?
PublishRank is another free WordPress SEO plugin option, with a focus on technical
SEO and publisher workflows such as News XML sitemaps, redirects, robots controls,
schema, and link auditing. It is not a drop-in clone of Yoast SEO or Rank Math,
and feature coverage differs. Review compatibility and avoid letting multiple plugins
output duplicate titles, canonicals, robots directives or schema.
### Is PublishRank only for news websites?
No. It is designed with publishers in mind but can also be used on blogs, business
websites and other WordPress sites.
### Does PublishRank require a paid API key?
No. The core plugin runs locally. IndexNow is optional and uses the public IndexNow
service when enabled by an administrator.
### Does IndexNow guarantee indexing or submit URLs to Google?
No. IndexNow requests are shared with participating search engines, but acceptance
does not guarantee crawling or indexing. Google does not support IndexNow.
### Can I use PublishRank with another SEO plugin?
The plugin can detect several SEO plugins, but two plugins outputting titles, canonicals,
robots tags or schema at the same time can create duplicates. Configure only one
plugin to own each output.
### Does PublishRank add a visible public credit?
No. PublishRank adds no visible credit to your site footer. Technical source provenance
is disclosed in PublishRank Settings and always remains enabled on public HTML pages.
### Where can I find documentation and support?
Visit the [PublishRank website](https://publishrankseo.vercel.app/) for documentation
and support information.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“PublishRank” is open source software. The following people have contributed to
this plugin.
Contributors
* [ umarjaum ](https://profiles.wordpress.org/umarjaum/)
[Translate “PublishRank” into your language.](https://translate.wordpress.org/projects/wp-plugins/publishrank)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/publishrank/), check
out the [SVN repository](https://plugins.svn.wordpress.org/publishrank/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/publishrank/) by
[RSS](https://plugins.trac.wordpress.org/log/publishrank/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 2.9.110
* Added **Setup Wizard** directly under Dashboard in the PublishRank sidebar (also
kept in the dashboard hero, workflow card, Plugins row and toolbar).
* Added the animated PublishRank logo as a loader on every PublishRank admin screen,
with a CSS-only failsafe and an opt-out (`data-pr-no-loader`) for forms.
* Redesigned the Dashboard and screen headers to match the official website: white
header bar, pink hero with a live preview of your site checks, pill buttons,
feature strip and a three-step publishing workflow (`assets/css/website-theme.
css`).
* Added the official website, https://publishrankseo.vercel.app/, to the plugin
header, Plugins screen (Official Website), dashboard, Documentation & Help, front-
end credit and readme, replacing the old netlify address.
* Made the version consistent: plugin header, `PUBLISHRANK_SEO_VERSION`, readme
stable tag, Branding fallback, docs and in-dashboard documentation all read 2.9.110(
documentation previously still said 2.9.105 and 2.9.108).
* Restructured `docs/` into getting-started, features, admin and maintenance folders
with a new index, installation guide and setup-wizard guide.
* Synchronised the reviewable `src/assets` copies with the shipped `assets` files.
* Fixed the loader staying on screen after export/download actions; it now skips
download links and forms and always hides after 12 seconds.
* Newsroom attachments notice now only appears on PublishRank screens and explains
the fix; added the optional `PUBLISHRANK_PRIVATE_DIR` constant (and `publishrank_private_storage_base`
filter) for hosts that need a custom private folder outside the web root.
* Uninstall now also removes Newsroom (`uj_newsroom_*`) options and the weekly-
audit and sitemap-cursor scheduled tasks.
* Added `tools/check-version.sh` and `VersionConsistencyTest` to keep versions
consistent.
#### 2.9.109
* Align the WordPress-loaded admin palette with the PublishRank website brand colors.
* Replace the plugin menu mark with the supplied PublishRank menu icon and refresh
asset cache keys.
* Render a blank 404 log table body after the log is cleared.
#### 2.9.108
* Improved dashboard tool-search feedback: the live result count shows matching
tools out of the available total, with localized announcements for assistive
technology.
* Corrected the WordPress readme stable tag and outdated guidance about template
variables in social metadata.
* Organization/WebSite JSON-LD is now omitted until publication and publisher names
are configured, avoiding empty identity nodes and broken graph references; the
Schema screen links to the setup wizard when identity is incomplete.
* Kept story-specific Web Story logos out of the site-wide Organization entity
and preserved alt text and dimensions for attachment-backed default social images,
including CDN URL rewriting.
* Redirect cycle checks now include active regex rules and fail closed when the
configured chain-analysis depth is exceeded. Foreign-host source URLs are rejected,
and the supported 303 status is selectable in the form.
* Added regression tests for publisher graph readiness and redirect source/cycle
safety.
* Added an opt-in SEO ownership handoff: when enabled, PublishRank suppresses its
overlapping frontend metadata, hreflang and page JSON-LD only when a supported
SEO plugin is detected. Warning-only behavior remains the default; external plugin
settings, redirects, sitemaps and standalone schema feeds are not changed.
* Added regression tests for handoff defaults, supported-plugin detection and the
separation between saved preferences and effective frontend output.
* Newsroom private attachments now use a writable directory outside DOCUMENT_ROOT,
migrate existing uploads without changing stored file IDs, serve only through
the authorized download handler, and fail closed for new uploads if private storage
is unavailable.
* Added sitewide wp-admin Newsroom pop-up alerts and a recent-notifications inbox
for assignment, stage, overdue-reminder and discussion events, with per-user
email, in-app and pop-up preferences. AJAX polling and read actions require Newsroom
access and a nonce; notification records are scoped to stories the user can still
access.
* Added Newsroom export-filter and adjacent-stage regression coverage and stage-
change success feedback.
* Moved Newsroom notifications into a dedicated bell tab with server-rendered and
live unread counts, clearer dashboard naming, and keyboard-friendly notification
badges.
* Restricted role-matrix changes to administrators, added a separately delegable
setup-wizard capability, preserved administrator access, and hardened nested
role input handling against malformed requests.
* Fixed duplicate breadcrumb schema output by collapsing multiple BreadcrumbList
nodes to one canonical list and removing repeated breadcrumb items with the same
label and URL.
* Extended the 404 monitor with request normalization, common probe suppression,
GET/HEAD filtering, crawler classification, short-lived write locking, 90-day
retention, safer referrer/path limits, and searchable/sortable admin summaries.
* Added dedicated 404 Monitor documentation covering privacy, capture exclusions,
throttling, retention, filters, redirect validation, dismissal, clearing and
troubleshooting in the package, readme and in-dashboard help.
* Added a complete versioned feature inventory for PublishRank 2.9.108, covering
all dashboard cards and all Technical Health checks shown in the supplied dashboard
reference image.
#### 2.9.105
* New: Google Preferred Sources tool (PublishRank Google Preferred Sources), shown
with a “New” badge in the menu and on the dashboard until you open it.
* Generates your Preferred Sources link (https://www.google.com/preferences/source?
q=DOMAIN) from the site’s home URL or an address you enter; paths, queries and
fragments are removed, unsafe schemes are rejected and internationalized domains
are preserved.
* Shows Google’s documented button code (div with google-add-preferred-source-btn
plus the official publisher.js script) with Copy, a placeholder preview, optional
documented data-theme and data-lang, and Reset to Default.
* Custom Button Builder generates an accessible, independently styled link to your
Preferred Sources URL, clearly labelled as a custom link and not Google’s official
button, because Google documents no custom styling for its own button.
* Advanced HTML editor with warnings, strict allow-list validation, no code execution,
and exact saving (code that fails validation is not saved or rewritten).
* Optional automatic placement (off by default): top of page, above, middle or
below the article, or footer, on the page types you choose. The button is printed
in the normal page flow with its own spacing so it does not overlap theme content.
Google’s script is added only when Google’s button is shown, never in wp-admin.
* One simple panel: choose Default or Custom once, then choose where it appears.
* Shortened the PublishRank sidebar to Dashboard, Newsroom, Settings and Documentation.
Every other tool, including all Newsroom screens, is reached from a Dashboard
card and remains registered, so direct links keep working.
#### 2.9.104
* Corrected the default breadcrumb root to “Home” with the site’s actual homepage
URL. Publication identity remains unchanged in document titles, publisher/WebSite
schema, Open Graph, and other SEO output.
* Added an expandable PublishRank admin navigation with keyboard-accessible dropdown
groups for Content & publishing, Newsroom, Search & discovery, Measure & maintain,
and Settings & support.
* Added distinct Dashicons for PublishRank tools; they follow the menu text color
with no custom tile or background.
* Fixed the dashboard authorization regression by retaining all registered PublishRank
submenu destinations in WordPress’s submenu registry.
* Fixed Schema Aggregator descriptions so SEO template variables such as `%%focus_keyword%%`
and `%%excerpt%%` are resolved before public JSON-LD is generated.
* Added the supplied PublishRank brand mark to the packaged assets and documented
the navigation/accessibility changes.
* Replaced every icon with the single official PublishRank mark (`assets/images/
publishrank-brand-mark.png`) in the admin sidebar, toolbar and its dropdown,
screen headers, setup wizard and sitemap view. The extra PNG icon sizes and `
publishrank.svg` were removed from the package.
* Removed the custom dark background and the coloured icon tiles from the PublishRank
admin dropdown; it now uses WordPress’s native submenu colours, so it follows
every admin colour scheme. The Dashboard entry shows the PublishRank mark.
* Redesigned the XML sitemap view in the bordeaux-to-pink brand palette: branded
header, showcase hero with the PublishRank mark, summary tiles, a content showcase
bar with per-type URL shares, colour-coded type cards with URL counts, light
and dark modes, and a version footer.
* Made the version consistent everywhere: the Branding fallback and the Newsroom
module now follow `PUBLISHRANK_SEO_VERSION` (2.9.104); sitemap view and admin
headers display the same number; the readme changelog headings were corrected.
* Fixed the sidebar and dropdown icons not updating or not showing: the menu stylesheet
and onboarding stylesheet are now cache-busted by file time (they were cached
under the unchanged version number), and the brand mark is drawn as a plain background
image instead of a CSS mask, which browsers refuse to paint for cross-origin
assets.
* Bumped the internal integrity build marker (not the plugin version) so the file-
integrity baseline is rebuilt after this package replaces the earlier 2.9.104
files, which otherwise reported changed PHP files.
* Expanded the documentation: new in-dashboard sections (menu and toolbar, sitemap
view, live blogs and Newsroom, versions, troubleshooting) and a new `docs/` folder
with guides for sitemaps, branding, navigation, troubleshooting, versioning and
a compatibility checklist.
#### 2.9.103
* Updated the admin palette using a navy/teal analogous foundation with coral action
accents and gold attention states.
* Improved contrast and focus colors across dashboard, onboarding, status badges,
and tool filters.
#### 2.9.102
* Added a dashboard Tools Showcase search and category filter and reduced the native
PublishRank submenu to essential destinations while preserving direct tool access
from the dashboard.
* Changed: visible PublishRank breadcrumbs are enabled after upgrading to 2.9.102,
including sites that had the visibility option saved as off. Publishers can still
switch them off later from PublishRank > Breadcrumbs.
* Improved: the Breadcrumbs screen now shows a clear recommendation to disable
the theme or page-builder’s own visible breadcrumb renderer when using PublishRank,
to avoid duplicate trails. PublishRank does not silently disable theme settings.
* Added: regression coverage for the visibility checkbox and duplicate-breadcrumb
recommendation.
#### 2.9.101
* Fixed homepage SEO template variables appearing literally in wizard and dashboard
configuration summaries.
* Unified administrative homepage-title previews with the frontend template resolver
and added a responsive dashboard identity/title summary.
#### 2.9.99
* Added: PublishRank’s publication title and description now override the WordPress
Site Title and Tagline on the public website (on by default; Settings > Visible
publication identity). Themes, block themes, Elementor widgets, feeds, the REST
index and get_bloginfo() show the PublishRank values after a single setup. The
values stored in Settings > General are never written or changed, wp-admin and
the settings REST route still see the real WordPress values, and a PublishRank
value that is empty leaves the WordPress value in place. A notice on Settings
> General explains the override.
* Note: the visible-identity hiding from 2.9.98 is a separate switch and is still
on by default, so the theme’s visible title and tagline stay hidden on screen.
Turn “Hide the visible site/publication title” off to show the (now PublishRank-
provided) title in the header.
* Added: tests/cases/10_identity_override.php.
#### 2.9.98
* Changed: the publication (website) title and description are owned by PublishRank.
They are read only from PublishRank settings (publication name / Identity name,
Identity description) and are never taken from the WordPress Site Title or Tagline:
titles and the %%sitename%% / %%site_description%% variables, meta description,
Open Graph, WebSite/Organization schema, breadcrumbs, sitemaps and stylesheet,
llms.txt, Live Preview and audit e-mails all use the same PublicationProfile
values. Nothing is copied from WordPress on install or in the wizard any more;
values already saved by earlier versions are kept untouched. When a value is
empty the dependent output is left out and PublishRank screens show a notice
asking for it.
* Changed: the visible site title and tagline printed by the theme are hidden on
screen by default on every public page (both switches default to on; an explicit
earlier choice is kept, and each can be turned off in Settings). The rule is
visually-hidden instead of display:none, so the text stays available to screen
readers and crawlers; SEO output is unchanged. Added Elementor site-title widget
selectors and the `publishrank_hidden_identity_selectors` filter.
* Note: sites that never saved the two switches become hidden after the update;
turn them off in Settings > Visible publication identity if your header uses
the site title as its logo text.
* Added: tests/cases/09_publication_identity.php.
#### 2.9.97
* Fixed (root causes of missing visible trails): automatic placement only existed
for singular views via the content filter, so archives, the posts page and any
template that does not run the main-loop content filter (Elementor theme-builder
templates, Canvas/Header-Footer page templates) printed nothing while BreadcrumbList
JSON-LD was still output. Added placement for classic archives (main loop start),
block-theme archives (above the archive title) and block-theme templates without
a title block (above post content), plus the documented Elementor hooks `elementor/
widget/render_content` (Pro title widgets) and `elementor/page_templates/canvas
|header-footer/before_content`. With Elementor loaded, the content filter is
also accepted outside the main loop (never during wp_head).
* Fixed: duplicate prevention used one request-wide flag; it is now a per-context
registry (main-query object), and the manual-trail check also reads Elementor`
_elementor_data` shortcode widgets. A trail printed by a shortcode no longer
blocks unrelated contexts.
* Fixed: the shortcode and Breadcrumbs block now respect “Print the breadcrumb
trail on the site” (off = nothing). Placement “Structured data only” still allows
a hand-placed trail, as before.
* Fixed: the static front page no longer gets a “Home › Home” trail or BreadcrumbList(
opt in with the `publishrank_breadcrumb_show_on_front_page` filter); the posts
page now gets Home › Posts page.
* Fixed: BreadcrumbList suppression assumed another SEO plugin emitted breadcrumb
data whenever its function existed. Yoast SEO and Rank Math are now checked against
their own breadcrumb setting; All in One SEO is only released when its option
explicitly reads off (option path not verified on a live install). Use the `publishrank_breadcrumb_schema_external_owner`
filter to override.
* Fixed: the site check counted the separator `` as a second renderer (false “multiple trails” warning) and counted
the word BreadcrumbList inside text; it now decodes the JSON-LD.
* Improved: the Breadcrumbs site check tests an article, a page and a category
archive, shows HTTP status and the settings in force, and separates confirmed
facts (settings, markup, a one-time probe note printed by the plugin during that
request) from unconfirmed candidate causes. It reports disabled/manual/schema-
only settings, unregistered placement, too few items, hooks that never ran, PublishRank
markup, other plugin or theme markup, stylesheet/inline-hiding checks, multiple
trails, multiple or dangling BreadcrumbList, cache hints and fetch errors. Administrator-
only, nonce-protected, rate-limited to one run per 20 seconds, own-site URLs
only, never on visitor requests.
* Improved: breadcrumb stylesheet is versioned by file time and scoped to `.publishrank-
breadcrumbs` (own row in Elementor/flex containers); no `!important`.
* Added: tests/cases/08_breadcrumb_placement_and_diagnostics.php.
#### 2.9.96
* Hardened frontend visibility detection for WordPress installations where `is_rest()`
is not available.
* Retained the breadcrumb detector improvements for quoted markup and page/post
site checks.
#### 2.9.95
* Breadcrumb site checks now detect both single- and double-quoted class attributes
and inspect the latest published post or page.
* Added optional visual-only controls to hide the visible publication/site title
and/or description on the home page, pages and posts. SEO metadata, schema, feeds
and General Settings values are unchanged.
* Added the new visibility settings to installer defaults, Settings, import/export
and configuration snapshots; both controls are off by default.
#### 2.9.94
* Breadcrumbs screen: added an actual latest-published-post preview using the site’s
real publication, category, title and URLs, plus a JSON-LD item preview that
never includes the visual separator.
* Breadcrumbs screen: exposed look, size, colors, invalid-item recovery, fallback
URL/label and local error logging in the same save form.
* Breadcrumb settings now validate and persist all appearance and recovery controls
together with the visible trail, separator, placement and schema switches.
#### 2.9.93
* Fixed literal `\\n` provenance text and duplicate SEO branding markers in frontend
HTML.
* Resolved article schema descriptions through the same template resolver as meta,
Open Graph and X/Twitter descriptions so `%%variables%%` never reach JSON-LD.
* Treat `%%sep%%` as title-only in descriptions, including older saved description
templates, so separators cannot leak into meta descriptions.
#### 2.9.92
* Added: a grouped “Insert variable” dropdown under the SEO title, meta description,
social title and social description fields in the post editor, in the Live Preview
snippet editor and on the setup wizard’s homepage title and description. It lists
every variable the plugin resolves (Site, Content, Author, Taxonomy, Dates, SEO),
explains each one and what it returns when empty, inserts the exact token at
the cursor without touching the rest of the text, is a native select (keyboard
and mobile friendly) and also works in fields the block editor adds later.
* Added: Meta\TemplateVariables, one registry of variables (token, label, description,
contexts, fallback). The resolver’s list of supported names is now read from
it, so the dropdown, help text and resolver cannot disagree. Variables unavailable
for a content type (for example categories on pages) are shown disabled with
the reason.
* Fixed: social title and social description overrides did not resolve variables,
so a template such as %%title%% was printed literally in og:title, og:description,
twitter:title, twitter:description and in the REST/preview data. They now go
through the same resolver; unknown tokens are dropped and an empty result falls
back to the SEO title/description.
* Fixed: the Live Preview snippet editor offered only a legacy “Insert %focus_keyword%”
button; it now uses the full dropdown. Help text lists are generated from the
registry.
* Added: Breadcrumbs screen (dashboard card “Breadcrumbs”): visible trail on/off,
frontend override, separator preset list and custom Unicode separator with live
preview, placement and theme hook, first-crumb label, BreadcrumbList on/off,
and a site check that reports which breadcrumb renderers the live page prints
and warns about duplicate trails or duplicate BreadcrumbList blocks.
* Added: frontend override option (publishrank_breadcrumb_frontend_override, on
by default, existing choices untouched). When on, PublishRank’s separator is
applied through the separator filters of Yoast SEO, Rank Math, WooCommerce and
All in One SEO instead of editing HTML. Off leaves those plugins untouched. Extend
with the publishrank_breadcrumb_override_filters filter.
* Added: separator presets “»»” and “…”.
* Note: PublishRank contains no code that reads All in One SEO settings, so a separator
that survives that plugin’s removal comes from the theme, cached pages or leftover
content. Use Breadcrumbs > Site check to identify the source.
* Added: tests 05 (registry, resolver agreement, social resolution) and 06 (override,
separators, detector, screen).
#### 2.9.91
* Fixed: global SEO title templates and per-post SEO titles/descriptions now share
one resolver (Meta\TemplateResolver). Global templates previously supported only
8 variables; both places now support the same 15: %%title%%, %%sitename%%, %%
site_description%%, %%category%%, %%primary_category%%, %%author%%, %%date%%,%%
modified%%, %%excerpt%%, %%sep%%, %%page%%, %%id%%, %%permalink%%, %%focus_keyword%%
and %%focuskw%% (the legacy %focus_keyword% / %focuskw% forms still work). Unknown
variables are dropped, values are never re-expanded, and dangling separators
left by empty values are removed.
* Fixed: saving %%date%% or %%category%% in a title/description template (post
editor, REST, settings, import) corrupted it to “%te%%” / “%tegory%%” because
sanitize_text_field() strips percent-encoded sequences. Templates are now sanitized
token-safely. The upgrade repairs these two corrupted forms in the global templates
and homepage title/description; per-post values already damaged on a site are
not rewritten automatically.
* Fixed: the REST/dashboard view of a post’s meta description did not resolve variables
and could differ from the front end.
* Fixed: spaced breadcrumb separators (for example ” › “, “» “) lost their spaces
on save, and “no separator” and a non-breaking space could not be stored. Separators
are now validated by a dedicated sanitizer: plain text only, up to 10 characters,
markup/control/bidi characters removed, invalid input rejected with a notice
and the previous value kept.
* Added: grouped breadcrumb separator presets (arrows, angles, slashes and lines,
dots and bullets, dashes, other symbols, spaced variants, space / non-breaking
space / none), a custom field and a live preview. Existing saved choices keep
showing as presets.
* Changed: right-to-left mirroring now applies only to directional separators (
arrows and angle brackets), and separators keep their spacing (white-space: pre).
* Fixed: when BreadcrumbList output was off, the WebPage node still pointed at
a BreadcrumbList that was not printed. The reference is now only emitted when
the list is.
* Added: separate “Organization and WebSite entities” switch (publishrank_org_website_schema_enabled,
default on). Turning it off removes those two entities and every reference to
them while keeping the WebPage/Article/BreadcrumbList entities valid.
* Changed: every output switch (metadata, schema, organization/website, visible
breadcrumbs, BreadcrumbList) is read through one helper, is honoured at run time(
including the document title), and treats a missing option as enabled and a saved
false-like value as disabled.
* Changed: BreadcrumbList is not added when Rank Math or All in One SEO already
prints breadcrumbs (as was already the case for Yoast SEO); the filter publishrank_breadcrumb_schema_external_owner
can override this.
* Fixed: with the block-theme automatic placement, a trail placed by hand (block
or shortcode) in the post no longer produces a second trail.
* Added: saving any identity, schema, social, breadcrumb, title-template or output-
switch option clears per-request caches, bumps the cache epoch and schema-index
generation, and fires the publishrank_seo_output_settings_changed action for
page-cache plugins.
* Upgrade: safe to repeat; existing explicit on/off choices are kept, missing switches
are created enabled.
* Added: automated integration tests (tests/), run against a real WordPress install.
#### 2.9.90
* Expanded dynamic variables for per-post SEO titles and meta descriptions, including
title, site name, category, author, dates, excerpt, separator, page number, post
ID, permalink and focus keyword.
* Improved post-editor help and token-based placeholders so reusable templates
are easier to compose.
* Expanded title-separator and visible breadcrumb-separator presets while preserving
custom separator support.
* Existing frontend schema and breadcrumb controls remain configurable and default
to enabled.
#### 2.9.89
* Added Crawl Optimization settings for removing optional WordPress head metadata,
feed discovery links, emoji assets, and selected response headers.
* Added opt-in internal-search cleanup, pretty-search URL normalization, search
query length/special-character/spam filters, UTM URL-bar cleanup using the History
API, and conservative unknown-query-parameter redirects.
* Added optional robots.txt rules for the WordPress core REST content API namespace
and internal search URLs. PublishRank’s schema index endpoint remains outside
the blocked core REST namespace.
* All new crawl optimization controls default to off; feed endpoints are not forcibly
disabled.
#### 2.9.88
* Added a public, paginated REST schema-discovery index at `/wp-json/publishrank/
v1/schema-index` for public, published, non-password-protected content. It lists
canonical URLs, schema types, titles, publication/modification dates, and available
summaries/images without exposing full article bodies or private content.
* Linked the schema-discovery endpoint from generated `llms.txt` resources when
schema output is enabled. The complete JSON-LD graph remains on each canonical
content URL.
* Added short-lived response caching and cache-generation invalidation when content
changes.
* Deferred Newsroom-related work; this release focuses on AI-oriented schema discovery.
#### 2.9.76
* Corrected the attribution disclosure to describe the always-on technical source
markers accurately and remove references to a visible footer-credit toggle.
* Updated release and security regression tests to match the 2.9.75 package, including
the removed remote News feed and admin nonce requirements.
#### 2.9.75
* Removed the optional live News feed (remote announcements.json request) and its
admin screen, prompt, styles and script; the plugin no longer requests remote
announcement data or remote images.
* Removed WordPress.org directory asset files (icons, banners, social images) from
the plugin package; they are uploaded separately through SVN.
* The sitemap stylesheet (XSL) now embeds the bundled sitemap CSS and JavaScript
from the plugin’s own local files instead of linking them.
* Removed the optional Publisher Account sign-in (Netlify Identity / Supabase)
screen, its admin-screen gate and the related settings, and the hosted Google
sign-in broker. Search Console now connects only with your own Google OAuth client
ID and secret; Disconnect also revokes the grant at Google.
* Traffic Guard: IPv4-mapped IPv6 addresses now match IPv4 rules; networks broader
than /8 (IPv4) or /16 (IPv6) are rejected; genuine search-engine crawlers (verified
by reverse and forward DNS) are never blocked unless this is switched off; blocked
responses are sent with no-store headers and DONOTCACHEPAGE; the settings screen
shows the detected IP/country and warns when your own address would match a block
rule.
* Added explicit nonce and capability verification inside every handler that reads
submitted data, and the live-preview request.
#### 2.9.74
* Sitemap stylesheet (XSL) no longer prints inline style/script blocks; its CSS
and JavaScript are served from bundled assets/css/sitemap.css and assets/js/sitemap.
js.
* Sanitized all remaining $_POST, $_GET, $_REQUEST, $_COOKIE, $_SERVER and $_FILES
reads at the point of use (AdminAccess, TrafficGuard, redirects, 404 monitor,
import, Baidu, post meta, local SEO, onboarding, live blog, internal links, authentication
and Search Console forms).
* Verification files are filtered through a strict tag allow-list before saving
and when served, and are output with wp_kses().
* Escaped output late for the editor score ring, live bar, verification meta tags,
schema-type dropdown and JSON-LD (JSON-LD no longer uses JSON_UNESCAPED_SLASHES).
#### 2.9.73
* Losslessly recompressed four shipped PNG/GIF assets while preserving original
formats, dimensions, exact decoded pixels, and GIF frame timing.
* Reduced the combined size of the 20 shipped PNG/GIF assets by 134,976 bytes (
3.31%); no external image or font services were added.
* Synchronized the plugin header, runtime version constant, and stable tag to 2.9.73.
#### 2.9.72
* Changed the optional live News JSON source to the official public `announcements.
json` in the PublishRank website repository and accepted GitHub Raw’s `text/plain`
response while continuing to validate JSON schema.
* Added a branded, dismissible first-activation consent dialog with explicit enable,
decline, and not-now choices; no News request occurs unless the administrator
opts in.
* Disclosed GitHub Raw, the canonical GitHub source, and the separate Netlify image/
link host before opt-in and in WordPress privacy-policy/readme documentation.
* Rendered the top-level sidebar icon as an alpha-masked, solid-white silhouette
to match the PublishRank header icon.
* Synchronized the plugin version header, runtime constant, and stable tag to 2.9.72.
#### 2.9.71
* Added the explicitly opt-in PublishRank News admin screen, backed by a validated
and cached live JSON announcements feed, with images, summaries, expandable details
and approved links.
* Added capability- and nonce-protected enable, refresh and disable actions, safe
feed parsing, strict same-host HTTPS media/link allowlisting, stale-cache fallback
and opt-out cache cleanup.
* Added a detailed News feed operations/privacy guide and disclosed the external
service in the privacy policy text and WordPress.org readme.
* Synchronized the plugin header, runtime constant and stable tag to 2.9.71.
#### 2.9.70
* Added optional Netlify Identity linking for existing WordPress administrators;
the feature does not create WordPress users or change roles.
* Corrected error-level WordPress coding-standard findings across PHP source.
* Added a PHP-scoped project PHPCS ruleset; warnings stay visible and non-blocking
after errors are cleared.
* Updated source-level regression assertions to tolerate harmless formatting changes.
#### 2.9.55
* Fixed fallback injection of technical provenance and SEO head output for themes
that omit `wp_head()`, without duplicate markers.
* Explicitly flush PublishRank-owned frontend fallback buffers at shutdown when
safe, without closing buffers owned by other plugins.
* Added direct-web-access guards to standalone regression scripts and aligned version
fixtures/fallbacks with 2.9.55.
#### 2.9.54
* Made technical source provenance markers always-on and removed the administrator
toggle.
* Updated settings copy and documentation to distinguish source markers from visible
footer branding.
#### 2.9.52
* Added a responsive activation welcome screen with a quick-start guide and clearer
legal disclosure for optional public attribution.
* Improved PublishRank toolbar and dashboard menu alignment across desktop, folded-
sidebar and mobile admin layouts; shipped a white icon treatment for dark WordPress
chrome.
* New one-click **Sign in with Google** for Search Console: no OAuth client ID
or secret to create. The site is matched to its Search Console property automatically.
* Live data: Search Console clicks, impressions, 48-hour hourly chart, top queries
and articles, Google Discover and Google News totals refresh hourly in the background
and update on screen every 15 seconds through WordPress Heartbeat, alongside
a newsroom feed (articles published, SEO scores, IndexNow queue, 404s). A Live
status bar appears under every PublishRank header.
* Publisher Account now offers Continue with Google first and lists only the sign-
in providers that are enabled on the Supabase project.
* Updated the admin visual system to warm editorial paper, deep plum, evergreen
and brass, with high-contrast controls and accessible status colors.
* Replaced the dashboard’s duplicate action lists with direct-action cards and
added a dedicated Traffic Guard workspace.
* Added opt-in local IP/CIDR deny and allow rules plus Cloudflare country blocking.
Forwarded IP and country headers are accepted only from explicitly configured
trusted proxies; unknown country data fails open, administrator and sitemap/API
routes are exempt, and no visitor IP is stored by Traffic Guard.
* Disconnecting Search Console now revokes Google access as well as deleting local
data.
* Live Preview in the post editor (block and classic): search snippet with pixel
and character meters, Facebook and X cards, every meta tag, the exact JSON-LD(
syntax-highlighted, copyable, with a Rich Results Test link) and a checks list.
It is built from your unsaved edits by the same code that outputs the page, nothing
is saved by previewing, and it refreshes as you type. REST: POST /publishrank/
v1/preview/{id} (users who can edit the post).
* Fixed: the article score card now reads the real SEO title, description and focus
keyword fields and the block-editor title.
* Fixed: JSON-LD identifiers could mix http and https on sites behind a proxy that
does not forward HTTPS, leaving references unresolved. The configured scheme
is now kept.
* XML sitemaps: styled index and child pages gain a type switcher, and Topics and
Authors now carry a lastmod in the index.
* robots.txt: new SEO-tool crawler group (Ahrefs, Semrush, Majestic, Moz, DataForSEO,
BLEXBot, PetalBot) with a one-click preset, optional WordPress housekeeping rules(
xmlrpc.php, wp-login.php, ?author= enumeration, REST users list, comment feeds),
WooCommerce cart and account rules, and protected paths that keep AI crawlers
out of paywalled or members-only areas. Per-crawler groups now repeat the low-
value and tracking rules instead of silently dropping them. Each section carries
its own explanatory comment.
* llms.txt: password-protected and noindex posts are never listed; About, Contact,
Editorial policy, Corrections, Ethics, Team and Privacy pages are detected and
listed first; authors, tags, custom post types and a machine-readable resources
section (sitemaps, news sitemap, robots.txt, RSS) were added; archives move under
the Optional section defined by the format; descriptions use the PublishRank
meta description and carry the publish date. llms-full.txt now has per-article
metadata (date, update, author, section), authority pages first, a per-article
word cap, a clean header and no empty summary line. Both files are cached until
content changes and answer conditional requests (ETag, Last-Modified, 304). The
settings …
## Meta
* Version **2.9.76**
* Last updated **1 day ago**
* Active installations **Fewer than 10**
* WordPress version ** 6.3 or higher **
* Tested up to **7.1.4**
* PHP version ** 7.4 or higher **
* Tags
* [news](https://wordpress.org/plugins/tags/news/)[redirects](https://wordpress.org/plugins/tags/redirects/)
[schema](https://wordpress.org/plugins/tags/schema/)[seo](https://wordpress.org/plugins/tags/seo/)
[sitemap](https://wordpress.org/plugins/tags/sitemap/)
* [Advanced View](https://wordpress.org/plugins/publishrank/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/publishrank/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/publishrank/reviews/)
## Contributors
* [ umarjaum ](https://profiles.wordpress.org/umarjaum/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/publishrank/)