The blog SEO checker that reviewed this very post

You are reading this on a blog that I write in a tool I built myself. It lives inside OScar, my personal life OS, and it comes with a blog SEO checker that graded this very post before it went live. This is a tour of that tool: the editor, the checks, the scheduling, and how my publishing agents hand it drafts. It is my own tool, not something I sell.

Fair warning: writing about an SEO checker while being checked by it is a strange experience. Every sentence I type, it is watching. Hello.

Why the blog moved out of the code

The first version of this blog was code. A post was a file, and publishing meant shipping a new version of the whole site. That is fine for one post a year. It is silly for anything more.

So the blog became a proper tool on my desk. Posts are written, saved, scheduled and published from there, and the public pages read the live posts straight away. A draft can never leak onto the site by accident, because the public pages only ever see posts that are published, or scheduled with their moment already passed.

The editor

The editor is the same rich-text kit as my notes, plus pictures. That means headings, bulleted and numbered lists, links, quotes, inline code and dividers. Pictures are shrunk to a light web format in the browser before they upload, and each one gets alt text, a short description for screen readers and search engines.

Beside the text sits the post's settings panel:

• Address: the slug, written for me from the title until I change it.
• Excerpt: the line on the blog list, also used when a description is missing.
• Cover picture with alt text, which becomes the preview when a post is shared.
• Tags, comma separated.
• Promotes: which tool on the site a post points readers towards, if any.

Everything autosaves a moment after I stop typing. There is no Save button to forget. The things that change what the world sees are separate, explicit buttons: Publish now, Schedule, Unpublish. A Preview button opens the post in the real public layout, visible only to me and hidden from search engines.

How the blog SEO checker works

The checker has two halves, and the split is the whole idea.

Half one: rules, live and free

Anything that can be measured is measured in code, instantly, as I type. No AI, no cost, no waiting. It checks things like:

• the title is between 30 and 60 characters,
• the search title fits in 60 characters, and the meta description sits around 120 to 160,
• the address is short, unique and free of filler words,
• the focus keyword shows up in the title, description, first paragraph, a subheading and the address,
• the keyword is not stuffed in so often that it reads like a robot wrote it,
• the post has enough words, subheadings in the right order, and no wall-of-text paragraphs,
• every picture has alt text and the cover has one too,
• there is at least one link to the rest of the site.

Each finding is a green pass, an amber warning or a red problem, with one sentence on why it matters and what to do. Next to them is a preview of how the post will look as a Google result. It is a surprisingly good way to notice a boring title.

This follows a rule that runs through all of OScar: a code rule beats a prompt line. If something can be checked exactly, it should be, rather than asking an AI to keep an eye on it.

Half two: one AI review, on request

Some things a rule cannot see. Does the post answer what someone searching for it actually wants? Is a section thin, padded or repeated? Is a subtopic missing that a reader would expect? Does it show real experience, with specifics and honesty?

For that there is a Run SEO check button. It runs the rules over the saved post and then makes one AI review of what the rules cannot measure. The rule results ride along, so the review does not repeat them. It also proposes a better title or description, but only when it would clearly earn more clicks.

The result is kept with the post, so I can come back to it later. I run it again after edits.

Problems never block publishing

This one is deliberate. The checker advises, it never vetoes. A red problem does not grey out the Publish button. Sometimes a short post is the right post. Sometimes the keyword simply does not fit a heading naturally, and forcing it would make the writing worse.

I decide. The checker just makes sure I decide with my eyes open.

Drafts, scheduling and unpublishing

Posts sit in three tabs: Drafts, Scheduled and Published. Each row is a real link, so I can open a post in a new tab like any web page.

Scheduling takes a date and a time on Stockholm's clock. The post goes live at that moment, and nothing has to wake up and flip a switch. The public pages simply start showing it once its time has passed. Unpublish sends a post back to draft. Delete asks first.

The public side gets the usual courtesies: proper search metadata, the cover as the sharing preview, the post in the sitemap, and an RSS feed for anyone who still loves RSS. I salute you.

Agents can write here too, as drafts

My Publishing tool, the one that runs my content sites, can deliver articles to this blog as well. I give an agent topics, it researches several sources and writes a post. The rule is firm: an agent's post always arrives as a draft. It waits here for the SEO check, my edits and my click.

If the agent later refreshes that article, the same post is updated in place. It keeps its address, its status and the SEO fields I set by hand. So an improvement never resets my own work, and a refresh never sneaks a draft live.

Writing a post with the checker watching

In practice the rules shape a post while it is being written. A missing keyword in the first paragraph shows up as amber before the paragraph is even finished. A heading that skips a level gets flagged the moment it appears. By the time I press Run SEO check, the boring fixes are usually done.

The AI review then has opinions, as AI reviews do. Some are good and make it in. The rest are politely ignored. That is the job description. The rules themselves follow the common advice in Google's own SEO starter guide, so none of them are mysterious.

Why build a blog tool at all?

Because writing should feel like writing, and checking should feel like help, not homework. Having the checker live beside the text, free and instant, means I fix things as I go instead of in a dreaded final pass.

If you want to see what else lives on the desk, have a look at OScar or the tools you can try yourself. And of course there is more to read on the blog.

Thanks for reading. The checker says you did great.