Skip to content

Changelog

What shipped in October

The month getReport became a daily publication, the Speed and Structured data modules grew up, the WordPress plugin reached wordpress.org and getReport Pro got its pricing page.

getReport team4 min read

October was the month the content side of getReport grew up. At the start of it we decided to publish one genuinely useful piece every single day, and then built the machinery so that decision keeps itself. The product kept moving underneath: a fuller Speed module, a rich results view, four new tools and a plugin you can now install from wordpress.org.

  • 27days in October with a new piece published
  • 4new free tools, bringing the total to 59
  • 2.2.3WordPress plugin version, now on wordpress.org

A piece a day, every day

From 5 October, a new guide or post went live every morning at 06:00 UTC: the error codes people actually search for (502, 503, 504, 403, 429 and the whole ERR_* family), a DNS cluster from what DNS is to reading a dig answer and WHOIS, the AI-search set (who answers, who cites, who crawls, Perplexity, brand visibility), fundamentals like what SEO is, what a reverse proxy does, the SSL handshake and what is inside an SSL certificate, and (in time for the season) the Black Friday website checklist.

Every piece follows the same bar: a diagram drawn for it, commands and configs that were actually run, sources named for every claim, and links into the tools so you can check your own site instead of taking our word. From November each guide also says who tested it, on which versions and when, and lists its primary sources at the end.

One topic a week from November

The daily guide keeps going, but from 2 November each week is one topic: a broad guide on Monday and six focused ones from Tuesday to Sunday. The first two weeks are Google AI Mode and AI search, then SSL errors browser by browser. The plan runs 52 weeks, to the end of October 2027, and every topic has a free tool you can run on the page. Blog posts like this one become their own track: the monthly changelog, data posts and behind-the-scenes notes, on top of the daily guide.

In the report

  • Speed module: page size and requests by type and by domain (with the share from other companies), the page's load events and the full request waterfall, all from data PageSpeed Insights already returns.
  • Time to First Byte from real users is now a scored check, next to the lab number, so a slow server shows up even when one test run was lucky.
  • Structured data module: a rich results view that shows which rich results each page is eligible for, the same way the schema validator now reports them.
  • Fixes: a running report always shows its progress and never sticks on Running, technology detection reads the page's markup rather than what its text says, and the XML sitemap generator says plainly that it crawls up to 100 pages.

New tools

Three AI tools joined the set on 8 October: the AI bot IP verifier (is that "GPTBot" in your log really OpenAI?), the NAP consistency checker (does your business name, address and phone match everywhere?) and the Wikidata checker. On 27 October the AI visibility checker followed: one run tells you whether AI assistants can read, quote and name your site. The hosting speed test now rates each first-byte number and says why two of them differ. The Tools menu lists every tool, with search and filters, and loads only when you open it.

The publishing system

Nothing above is posted by hand. How we publish every day without a CMS explains the whole thing: content is written and reviewed days ahead, merged with a future date and hidden until its day. Mid-month the gate moved from the build to the request: a piece now goes live at midnight UTC on its own, with no rebuild and no deploy, and one small scheduled job tells search engines. October also added a link checker that gates every change; a guide with a dead link, a missing image or no connection to the rest of the site cannot ship.

WordPress plugin on wordpress.org

The month opened with fix release 2.0.1: website scores resolve correctly for www sites, and the "connected" message says what is actually true. Versions 2.2.2 and 2.2.3 went through the wordpress.org review, and on 26 October the plugin was listed there. Every Get button on getreport.app now points to the listing, so updates arrive in your dashboard like any other plugin's.

getReport Pro: the pricing page

On 27 October the AI visibility tracking pricing page went up. getReport Pro is the one paid thing we will sell: scheduled tracking of what AI assistants say about your site, beyond the free tier of one site, three prompts and a monthly check. Founding reservations open once our payment provider approves the live account; nothing is charged before tracking starts. Every report, tool and one-off check stays free, with no account, as always.

Housekeeping

The site has a new footer with our social profiles, the header menus load on first use while keeping a plain list of links for crawlers, and our own uptime, certificate expiry and per-tool checks now alert us before you notice. The first monthly steering review of the content plan lands at the start of December.

How does your site compare?

Free report, no account, ready in under a minute.

Check my site

More posts

All posts →
Behind the scenes

How we publish every day without a CMS

getReport now ships one new guide or post every day for the next six months. There is no CMS behind it: markdown files, pull requests and one scheduled rebuild.

4 min read
Product

Check your site on every deploy

The getReport GitHub Action fails your build when a score drops. The story behind it, the design decisions, and a workflow you can paste in today.

9 min read