Description

Site Checkup — free, no account needed. Install, click SiteHale Site Checkup, and get an honest, read-only health check of your WordPress site, run locally in that page load:

Scheduled tasks — overdue WP-Cron events and Action Scheduler backlog. Dead cron silently stops scheduled posts, backups and update checks.
PHP errors — fatal errors hiding in logs nobody reads, plus oversized logs quietly eating disk.
Database health — autoloaded-options weight (the most common hidden cause of a slow site), expired transients, table overhead.
Updates & environment — pending core/plugin/theme updates, and whether your PHP and MySQL/MariaDB versions are past their security-support end dates.
SEO basics — is this site accidentally telling search engines not to index it (the classic post-migration mistake — and the weekly re-check alerts you if that switch ever flips), plain permalinks, whether anything is serving a sitemap, and whether any SEO plugin is writing your meta titles and descriptions.
Administrator audit — every admin account listed. A new admin you didn’t create is the classic compromise sign.
Outbound email test — one click proves whether your site can actually send mail, before a customer tells you the contact form is broken.

The checkup sends nothing anywhere — it reads your site and prints the results. It is yours, free, forever, with no account and no connection.

It tells you when it could not check. If your site’s PHP error log cannot be read — logging switched off, a custom log path, or PHP writing to the web server’s own file, which is normal on shared hosting — the checkup says exactly that, and marks the card “Could not check”. It will not show you a green tick it did not earn.

Checkup history & weekly re-check (also free, also local). Every checkup stores a compact snapshot (last 12, on your own site), so the page shows what changed since last time — “autoloaded options grew 40%”, “2 fewer fatal errors”. A weekly background re-check runs the same snapshot automatically, and if something regresses — a new administrator account, new fatal errors, cron gone overdue, an autoload jump — you get one dismissible admin notice. No regression, no notice, ever. The page also shows when the next automatic re-check is due, and warns you if it has stopped running — a plugin that promises a weekly check should be able to prove it is happening.

In Site Health too. The checkup result and the weekly re-check appear as tests under Tools Site Health, and a SiteHale panel is added to Site Health Info — the screen you copy into a support ticket when you need someone else to look. These read the last stored checkup, so they add no work to your dashboard.

An llms.txt for the AI era (free, automatic). The plugin serves a compact /llms.txt — your site’s name, tagline and an index of its published pages, posts and products — the emerging convention AI crawlers read the way search engines read a sitemap. It is built from your own published content and never goes stale. Deliberately polite: it stands down if anything else already serves that address (an SEO plugin’s version, or a real file), it is a summary rather than a full-content dump, and a site set to discourage search engines serves nothing. One filter switches it off.

Your SEO tags — and who else is writing them (free). SiteHale can render your titles, meta descriptions, social share tags and structured data, and the post editor shows you what it will serve for the page you are editing: the title, the meta description, the robots directives it asks for, the share image, and whether each value is one you wrote or one built from your templates. There is deliberately no score — it tells you what will be served, not how somebody grades it. It also names anything else on your site writing the same tags, because a theme or another plugin quietly emitting its own OpenGraph or meta description is a common reason the wrong title turns up in search results and on shared links. And if it has not looked at your front end since your last plugin or theme change, it says so rather than reporting a clean result it has not earned. Polite by default: on a site already running another SEO plugin, SiteHale stands down and the panel says so.

Email the checkup. Send yourself (or your developer) a plain-text copy of the results via your own site’s wp_mail(). An optional, off-by-default checkbox also shares the summary with SiteHale so a human can review it and reply with recommendations — that is the only way the free half of the plugin ever sends anything anywhere, and only if you tick the box.

The other half: SiteHale managed care. The checkup runs once, when you click it. The SiteHale service (https://sitehale.com) runs checks like these — plus SEO optimization, content work, verified backups and uptime monitoring — on a schedule, every week, with a human reviewing alerts and a monthly report you can actually read. If you connect, this plugin becomes the companion:

Connect — a one-click handshake using WordPress core’s own Application Passwords authorization screen. The plugin never creates users and never mints credentials itself; you approve access on WordPress’s native consent page, under your own account, and can revoke it any time from Users Profile.
Health diagnostics — read-only REST endpoints (the same data the Site Checkup shows) that let the SiteHale service watch over sites it cannot reach any other way. All endpoints require an Application Password plus administrator capability.
Care reports — your monthly SiteHale care report, rendered right in your dashboard: a dashboard widget with the latest summary plus a Care Reports page with the last 12 full reports. Reports are pushed by the SiteHale service (authenticated, size-limited, HTML sanitized on arrival).

Who builds it. SiteHale is built and operated by MacSolutions Plus, an Apple Authorized Service Provider in Buffalo, NY, in business since 2001. The checks in this plugin are the same ones we run across the sites we look after every week.

External services

This plugin connects to the SiteHale managed care service (https://sitehale.com), operated by the plugin author. It makes exactly four kinds of outbound requests to SiteHale, each strictly after an explicit administrator action, plus one optional request to a service that is not SiteHale (item 5, IndexNow — off unless you switch it on):

https://connect.sitehale.com/connect/facts — a one-time site snapshot (WordPress/PHP/database versions, theme, plugin list, permalink settings) sent when you click Connect, so the service can be configured for your site.
https://connect.sitehale.com/connect/pair — the Application Password you approved on WordPress’s authorization screen, sent once to complete the connection. WordPress core returns that credential to your own site, and the plugin forwards it from your server directly to SiteHale over an encrypted connection, so it is never placed in a web address or handled by your browser.
https://connect.sitehale.com/connect/checkup — sent ONLY when you tick the off-by-default “share with SiteHale” checkbox on the Email-this-checkup form: the checkup summary (the health lines shown on the page — no content, no visitor data) plus the email address you entered, so a SiteHale human can reply with recommendations.
https://connect.sitehale.com/connect/regression — sent only from sites with an active paid SiteHale plan, and only when the weekly background check finds that something got worse (a new administrator account, new fatal errors, cron stopping, an autoload jump, a version reaching end of support). It sends those finding lines plus your site address, plan name and plugin version, and — when the finding is a fatal error — up to three short excerpts (120 characters each) of the error messages themselves, so the fault can be identified rather than merely counted. Those excerpts are PHP error text and server file paths taken from your site’s own error log — no page content, no visitor data. This is what lets the notice on your own dashboard say the problem is already with SiteHale instead of asking you to go and look at it. On the free plan, and on a connected site with no plan, this request is never made.
https://api.indexnow.org/IndexNow — the only request in this plugin that goes to a third party, and the only feature that is off until you turn it on. IndexNow is an open protocol operated by Microsoft; submitting once shares the URL with Bing, Yandex, Seznam and Naver. (Google does not take part.) When you enable IndexNow on the SiteHale settings screen, then publish, update or unpublish a page, the plugin sends only that page’s web address, your site’s hostname, and a randomly generated key that identifies your site to the protocol — no page content, no visitor data, nothing about you. The key is also served as a plain-text file at https://your-site/<key>.txt, which the engines fetch to confirm the key is yours. URLs you have marked noindex, password-protected posts, and sites set to discourage search engines are never submitted. Unticking the box stops it and discards anything queued. IndexNow documentation: https://www.indexnow.org/ — Microsoft privacy statement: https://privacy.microsoft.com/privacystatement

No other outbound requests are made. The diagnostic and report endpoints are inbound: the SiteHale service calls your site, authenticated with the Application Password you approved. Disconnecting (or revoking the Application Password under Users Profile) fully stops all access and transmission. Service information, pricing, and support live at https://sitehale.com — see How It Works (https://sitehale.com/how-it-works/), Support (https://sitehale.com/support/), Privacy Policy (https://sitehale.com/privacy/), and Terms (https://sitehale.com/terms/).

Privacy

The free half of the plugin transmits nothing at all. The Site Checkup, its history, the weekly re-check and the regression notice run entirely on your own site, and are fully usable without an account, a connection, or a subscription. (On sites with an active paid plan, and only there, the weekly check reports what regressed to SiteHale so the service can act on it — item 4 under External services.)

The plugin makes no outbound request until you explicitly ask for one — clicking Connect, ticking the off-by-default “share with SiteHale” checkbox on the Email-this-checkup form, or switching on the off-by-default IndexNow setting (the only feature that sends anything to a third party, and then only the web address of a page you just changed — see item 5 under External services). When you connect, a one-time snapshot of your site’s environment (WordPress/PHP/database versions, theme, plugin list, permalink settings — no content, no visitor data) is sent to SiteHale so the service can be configured for your site. Disconnecting (or revoking the Application Password) fully stops all access and transmission.

Full policy: https://sitehale.com/privacy/ · Terms: https://sitehale.com/terms/

Screenshots

Installation

Using the free Site Checkup — no account, no configuration, no connection:

Install and activate the plugin.
Go to SiteHale Site Checkup. The checkup runs on that page load and shows your results immediately.
Optionally use Email me this checkup to send yourself a copy, and Send test email to prove outbound mail works.

That is the whole free setup. A weekly background re-check starts on its own and only speaks up if something regresses.

Optional — connecting to the paid SiteHale care service:

Go to SiteHale and click Connect to SiteHale.
Approve access on WordPress’s own Application Passwords authorization screen.
Connecting is free and does not sign you up for a paid plan. Care and Managed are paid monthly plans arranged directly with SiteHale; care reports appear under SiteHale Care Reports once you have a plan and it is active. Revoke any time from SiteHale Disconnect or Users Profile.

FAQ

Does this plugin slow my site down?

No. It adds no scripts, styles or blocks to your pages. The only thing it does on the front end is answer requests for /llms.txt — on every other page view its entire cost is one address comparison. The diagnostic endpoints only run when the SiteHale service calls them (authenticated), and each is a cheap, bounded read.

What data leaves my site?

Nothing, unless you ask. The Site Checkup and the weekly re-check are local on the free plan. Data leaves your site in four cases, all listed under External services: when you click Connect, when you tick the off-by-default share checkbox on the Email-this-checkup form, — on sites with an active paid plan only — when the weekly check finds something has regressed, and if you switch on IndexNow. In the first three the recipient is always SiteHale. IndexNow is the one exception and the reason it is off by default: it sends the web address of a page you just published or changed to api.indexnow.org, a Microsoft-operated service that shares it with Bing, Yandex, Seznam and Naver. Only the address — never your content, never anything about your visitors. Disconnect stops everything SiteHale receives; unticking IndexNow stops that.

Can I use this without a SiteHale subscription?

Yes — the Site Checkup page, its history, and the weekly background re-check are free, run entirely locally, and never expire. The Connect flow, remote diagnostics and monthly care reports are the parts that pair with the paid managed service.

Does clicking Connect start a subscription or charge me?

No — connecting by itself is free and never charges you. Care and Managed are paid monthly plans, and clicking Connect does not sign you up for one: it only pairs your site so a plan can be set up if you decide to buy one. Payment is never handled by the plugin — you arrange a plan directly with SiteHale, and it starts only once you have agreed to it. Connect without a plan and your site simply stays on Free. The SiteHale page shows your plan status (Free, Care, or Managed: not active / awaiting activation / active) at all times.

Does the weekly background check send anything anywhere?

Not on the free plan. It runs the same local snapshot the checkup page uses and stores the result on your own site. Its only visible output is a dismissible admin notice, and only when something actually regressed (a new admin account, new fatal errors, overdue cron, an autoload jump). A clean week produces nothing at all.

If you have an active paid SiteHale plan, a week that found a regression also reports those finding lines to SiteHale, together with a short excerpt of any fatal error message behind them — that is the point of the plan, and it is why the notice on a paid site says the problem is already being handled rather than asking you to investigate it. A clean week still sends nothing.

Will this plugin nag me with notices?

No. There are two, both dismissible, and neither follows you around the admin. The first only appears when the weekly check finds a regression, and a subsequent clean check clears it automatically; on a site with an active paid plan it is quieter still, showing the finding for information without asking you to do the work, because SiteHale is already handling it.

The second asks once whether you would review the plugin on WordPress.org. It appears only on SiteHale’s own screens — never on your Posts list or your dashboard — and only once it has been checking your site for a fortnight, with a couple of checkups on file, so you are being asked about something you have used. It never appears while a regression is outstanding: if the last thing we told you is that your site got worse, that is not the moment. “No thanks” removes it permanently, and nothing is offered in exchange for a review. If you would rather review it on your own terms — sooner than that, or after dismissing the ask — “Rate this plugin” sits on your Plugins list and a link sits in the footer of SiteHale’s own pages. Neither is a notice and neither ever interrupts you.

What is llms.txt, and why is my site serving one?

llms.txt is an emerging convention — a plain-text index at /llms.txt that AI assistants and crawlers read to understand what a site is and what it publishes, much as search engines read a sitemap. The plugin serves one automatically: your site’s name, tagline, and a bounded list of published pages, posts and products, rebuilt as you publish. It transmits nothing — it is content your site serves, exactly like a sitemap. It steps aside on its own if anything else already answers that address (an SEO plugin’s llms.txt, or a real file you uploaded), and a site set to discourage search engines serves none. To switch it off: add_filter( 'sitehale_llms_txt_enabled', '__return_false' );

Does it work on WordPress Multisite?

Yes, per site. The Site Checkup, its history and the weekly re-check are per-site, so each site in a network gets its own results, and each site connects to SiteHale separately if you want it to. Network-activating the plugin makes it available everywhere; only users who can manage a site’s options see it. Uninstalling from the network removes the plugin’s data from every site in it, not just the one you were on.

Where do I get support?

Managed clients: https://sitehale.com/support/ or plugins@sitehale.com. Free-plugin questions are welcome on the WordPress.org support forum for this plugin.

Reviews

KeithPublic 3 September 2026

I’ve been running an e-commerce store for years and have been through tech after tech. Plugins out of date, database bloated, never any time to write blog posts. SiteHale has completely taken it over. The free checkup was the first time I’d seen the whole list of what was actually wrong with the site in one place. Now I’m up to date, the blog posts are relevant and current, and the store runs much faster. What I appreciate most is the lack of nagging. It handles what it can handle, reports clearly on what it did, and gives me a plain message when something genuinely needs me — which is rarely. The reports are easy to understand and tell me everything SiteHale is taking care of.

Read all 1 review

Contributors & Developers

“SiteHale” adalah perisian sumber terbuka. Orang-orang berikut telah menyumbang kepada pemalam ini.

Translate “SiteHale” into your language.

Berminat dalam pembangunan?

Layari kod, periksa repositori SVN, atau langgani log pembangunan dengan RSS.

Changelog

0.7.62

Fixes a sitemap that was correct but served as “not found”. On a site whose front page is a fixed page and which has no blog posts, WordPress answers its own sitemap address with a “page not found” status while still printing a perfect sitemap. Search engines discard anything marked not found, so the sitemap was invisible to them while looking completely right in a browser — one site had been in that state for two weeks. SiteHale now keeps sitemap addresses out of WordPress’s not-found handling. Ordinary missing pages still return “not found” exactly as before.

0.7.61

Adds IndexNow, off until you switch it on. When you publish, update or unpublish a page, SiteHale can tell Bing, Yandex, Seznam and Naver immediately instead of waiting for them to crawl your site. (Google does not take part in IndexNow.) It is the only part of this plugin that sends anything to a service other than SiteHale, which is why it ships off and why the settings screen and the readme both say exactly what is sent: the web address of the page that changed, your hostname, and a key identifying your site — never your content, never anything about your visitors. Pages you have marked noindex, password-protected posts, and sites set to discourage search engines are never submitted, and unticking the box discards anything queued.

0.7.60

Author archives and attachment pages can now be kept out of search results, as a site-wide setting. Neither is a page anyone writes on purpose — an author archive on a one-writer site repeats the blog index at a second address, and its web address contains the account’s login name, while an attachment page is a bare wrapper around a single image. Both are left in search unless you switch this on; nothing changes on an existing site by itself.
Tag archives can now carry a SiteHale title, description and indexing setting. WordPress files blog tags under a different internal name than every other taxonomy, and SiteHale was asking for them by the wrong one — so its per-item SEO fields never attached to tag archives on any site. Nothing could be saved to one, and a tag set to be kept out of search would still have been listed in your sitemap. Categories, product categories and product tags were never affected.

0.7.59

“See what changed” now shows what was actually flagged. The link from the weekly notice led to the Site Checkup page, whose “since your last checkup” list compares against the most recent snapshot — which is the very run the notice came from, so the finding had already been absorbed into the baseline and could never appear. The page now shows the recorded finding itself, dated, above the current results.
A fatal-error finding now carries the error messages behind it, on the dashboard and in what a paid plan reports to SiteHale. A count on its own cannot tell fifty occurrences of one fault from fifty different ones, and the log has often rotated by the time anybody looks.
The checkup no longer congratulates you on errors that merely stopped being visible. The fatal count covers a rolling recent-log window, so it also falls when the log is cleared or rotated and when an old burst ages out of the window; both used to be reported as “N fewer fatal PHP errors than last time”. Those two cases now say what actually happened instead.

0.7.58

SiteHale’s diagnostics now report whether plugin auto-updates are switched on for this site, and for SiteHale itself. WordPress does not expose that over its REST API, so on a site SiteHale looks after without shell access there was previously no way to tell — and a site with auto-updates off silently stops receiving plugin releases without anything going wrong that you would notice. Read-only, like every other diagnostic here; it changes nothing about how your site updates.

0.7.57

Adds a panel to the post and page editor showing what SiteHale will render for that page — the title, the meta description, the robots directives it contributes, and the share image — and whether each value is one you wrote or one built from your templates. It shows saved values, so save the post to refresh them. There is deliberately no score: the panel tells you what will be served, not how somebody grades it.
The panel names anything else on your site writing the same tags. If your theme or another plugin adds its own OpenGraph or meta description on pages like the one you are editing, it says so and when it saw that. Duplicate tags are a common reason the wrong title shows up in search results and on shared links.
If SiteHale has not looked at your front end since your last plugin or theme change, the panel says that instead of reporting a clean result it has not actually checked.
The canonical URL and structured data are not in the panel — they depend on the live request — and it says so rather than quietly leaving them out.

0.7.55

The review request now counts a fortnight of checkups, rather than a fortnight since you first opened a SiteHale page. The old clock only started when somebody visited one of the plugin’s own screens, so on a site where nobody had, it never started at all and the request never appeared. If SiteHale has been checking your site for a couple of weeks it may now ask you once — on its own pages only, never while your site has an outstanding finding, and “No thanks” still removes it permanently.

0.7.54

Adds a permanent way to leave a review — “Rate this plugin” on your Plugins list, and a link in the footer of SiteHale’s own pages. Until now the only route was an occasional notice that waits two weeks after your first visit to a SiteHale screen, so on most sites it had never appeared and there was nowhere to click. Neither link interrupts anything, and both stay available whether or not you have dismissed that notice.

0.7.53

Site Checkup now recognises SiteHale itself as the SEO plugin on a site whose SEO it manages. Sites switched over to SiteHale were told “No SEO plugin detected” — and had the SEO section marked as needing attention for it — while SiteHale was writing their titles and descriptions. Sites using another SEO plugin, or none, are unaffected and read exactly as before.
Site Checkup now tells you who acts on each finding. On a Care or Managed site each section says whether SiteHale is handling it for you or watching it and alerting a human, so a section marked “Needs attention” no longer reads as a job waiting on you when it isn’t. The status itself is unchanged — it still describes your site, not your plan.
An end-of-life PHP or database version now says plainly that it is set in your hosting account and your host has to change it. No plan of ours can.
Fixes the free-plan footer disappearing on a site that had connected to SiteHale but was never activated. Connecting is free and provisions nothing, so those sites are on the free plan and should read like it.

0.7.52

Fixes a fatal error on hosts that run PHP without the mbstring extension. Shortening a title or description to fit its limit used a function those hosts do not provide, which could take down any page SiteHale generated one for. Nearly all hosts include mbstring and are unaffected; nothing else changes.

0.7.51

Housekeeping only, with no change to how the plugin behaves: tightens two internal code checks and shortens three update notices.

0.7.50

A product rated with stars but no written review now publishes its rating too. Previously only products with a written review did, so a product whose page showed “Rated 5.00 out of 5” could publish no rating at all.

0.7.49

Product pages now publish the brand, the star rating and customer reviews in their structured data, so shops keep their review stars in search results after switching over. Nothing is published for a product that has no reviews — an unrated product stays unrated rather than being shown as zero stars.

0.7.48

When SiteHale manages your SEO, a “page not found” address is no longer served with your home page’s title and description. It now returns a proper not-found title, tells search engines not to index it, and no longer names itself as the preferred address for a page that does not exist.
The one-click switch-over from your previous SEO plugin now also checks that your category and tag metadata was read, that something was actually examined, and that SiteHale has a reader for whichever plugin you are on. It stays closed rather than opening on an import that looked at nothing.
Category and tag metadata can now be read on sites with no server access, so those sites can complete a switch-over that previously counted your taxonomy pages as empty.
Re-importing your settings can no longer clear your business details when the address book they came from is switched off — a correction still applies, but “nothing to say” is no longer treated as “delete this”.
On a site whose previous SEO plugin was Yoast, the share image is no longer invented from your logo when Yoast never published one.
Leftover settings from an SEO plugin that has not run on the site for years are no longer read back in as current configuration during a re-import.

0.7.47

Business address and hours now update fully on re-import, so a correction always takes effect.

0.7.46

Opening hours are now published only when you have actually set them, never from the SEO plugin’s unused defaults.

0.7.45

Fixes the sitemap disappearing after switching SEO over to SiteHale.

0.7.44

Adds sitemap diagnostics, so a missing sitemap can be explained instead of guessed at.

0.7.43

Sites without server access can now have their site-wide SEO settings applied, completing the no-server-access import.

0.7.42

The option to switch your SEO over to SiteHale now appears only on sites with an active SiteHale plan.

0.7.41

Sites without server access can now carry their site-wide SEO settings across, not just their page titles and descriptions.

0.7.39

Keeps your sitemap working when SiteHale takes over from another SEO plugin, and carries site-wide settings across on sites without server access.

0.7.38

Fixes an error page that could appear on “not found” pages for sites using the new site-wide snippet settings.

0.7.37

Keeps site-wide search snippet settings when SiteHale takes over from another SEO plugin, so search results are not shortened.

0.7.36

Fixes over-long meta descriptions on pages that had none of their own — SiteHale was using the whole page as the description instead of a short summary.

0.7.35

Fixes sites whose SEO stayed paused after an update: SiteHale now checks several pages instead of betting on one, so a redirecting or members-only page no longer leaves the module switched off.

0.7.34

The “Turn on SiteHale SEO” switch now waits until your existing titles and descriptions have been copied across, so switching over cannot lose them.

0.7.33

Completes the update fix: SiteHale SEO now resumes fully after an update instead of getting halfway there.

0.7.32

Completes the 0.7.31 fix, which did not take effect on the update that introduced it. Updating the plugin no longer pauses SiteHale SEO.

0.7.31

Updating the plugin no longer pauses SiteHale SEO. It previously stopped managing your pages after each update until your site received a couple of visits, which on a quiet site could be hours.

0.7.30

Switching SiteHale SEO on now takes effect straight away instead of waiting for the next few visitors to your site.
After switching over, the SiteHale screen now confirms whether SEO is live — previously the button gave no acknowledgement at all.

0.7.29

The SEO switch-over is now one click. If a site runs more than one SEO plugin (for example All in One SEO alongside All in One SEO Pro), all of them are switched off together instead of one per click.
Add-ons belonging to the SEO plugin being switched off are now switched off too, which clears the “this add-on cannot be used” errors they otherwise leave behind.

0.7.28

Fixes the SEO handover notice not appearing right after install — the moment it is most needed.

0.7.27

SiteHale SEO now tells you when it cannot manage your SEO because another SEO plugin is active — and offers a one-click switch-over. Previously it stood down silently, so a site could sit for weeks with SiteHale SEO installed but idle.

0.7.26

SEO module: custom robots.txt rules are now carried over and served by SiteHale. Sites that had rules configured in a previous SEO plugin kept serving them; previously those lines disappeared when that plugin was switched off, so pages meant to stay out of search results — carts, checkouts, account pages — became crawlable.
SEO module: rules already present from WordPress or WooCommerce are not repeated, so robots.txt does not accumulate duplicate lines.
SEO module: a site set to discourage search engines keeps WordPress’s own robots.txt untouched.

0.7.25

SEO module: WooCommerce products now publish full product schema — price, currency, stock availability, SKU and category, with each variation of a variable product listed separately. Product pages previously published only page-level schema, so search engines could not see what was for sale or for how much.
SEO module: a product page no longer publishes an Article entry, which described the product as a blog post.
SEO module: WooCommerce’s own duplicate product markup is now stood down on pages where SiteHale publishes product schema, so the page describes each product once instead of twice.

0.7.24

SEO module: canonical and og:url now use the same address scheme (http or https) the page was requested on, instead of whatever is saved in your WordPress address setting.

0.7.23

SEO module: fixes the module refusing to manage SEO on sites using a block theme (Twenty Twenty-Four, Twenty Twenty-Five and similar), where it wrongly detected the theme’s own title tag as another SEO plugin.

0.7.22

SEO module: a separate blog page now uses the title and description you set on it, instead of falling back to your site title.

0.7.21

SEO module: social share images now publish their dimensions, so Facebook and LinkedIn lay the card out correctly instead of cropping or falling back to a thumbnail.

0.7.20

SEO module: your default social share image and Twitter card style are carried over from your previous SEO plugin, so pages without their own image still share with a picture.

Entries for 0.1.0–0.7.19 are in changelog.txt, shipped with the plugin:
https://plugins.svn.wordpress.org/sitehale/trunk/changelog.txt