by SEOWebChecker
Audit Markdown notes for on-page SEO, analyze heading hierarchy, keyword density, reading time, and inspect live URLs with SEOWebChecker.
SEOWebChecker SEO Audit — Obsidian Plugin
An advanced on-page SEO and readability auditing plugin for Obsidian, powered by SEOWebChecker.
Audit your Markdown notes, blog drafts, digital garden entries, documentation, and static site content (Hugo, Jekyll, Astro, Next.js) in real-time as you write.
Key Features
-
🎯 Real-Time SEO Health Score:
- Live 0–100 health score with academic grades (
A+throughF) updating seamlessly as you type. - Granular breakdown of Passes, Warnings, and Critical recommendations.
- Live 0–100 health score with academic grades (
-
📝 YAML Frontmatter Optimization:
- Validates
title/seo_titlelength (30–65 characters). - Validates
description/meta_descriptionsnippet length (120–165 characters). - Inspects
canonicalURL,slugkebab-case formatting, and keyword tags.
- Validates
-
📐 Heading Hierarchy & Document Structure:
- Ensures a single primary H1 heading (
#). - Detects skipped heading tiers (e.g. H1 jumping to H3 without H2).
- Displays full heading distribution counts across your article.
- Ensures a single primary H1 heading (
-
📖 Readability & Content Metrics:
- Calculates Flesch Reading Ease score and equivalent grade levels.
- Word count tracking against custom minimum and comprehensive targets.
- Estimates reading time and speaking time.
-
🔑 Focus Keyword Tracking:
- Specify your target term in frontmatter (
focus_keyword: "..."). - Analyzes presence in SEO Title, H1, introduction paragraph, and subheadings.
- Calculates keyword density percentage (recommends 1.0%–2.5%, warns if keyword stuffing > 3.0%).
- Specify your target term in frontmatter (
-
🖼️ Media & Link Diagnostics:
- Scans Markdown images (
) and flags missing or empty alt text. - Distinguishes internal wiki-links (
[[note]]) from external hyperlinks. - Detects generic, uninformative anchor text (e.g., "click here", "read more").
- Scans Markdown images (
-
🌐 Live Web Page Auditor:
- Direct integration to test published live URLs using Obsidian's secure
requestUrlAPI. - Evaluates HTTP response status, title, meta description, mobile viewport configuration, canonical links, and server latency.
- Direct integration to test published live URLs using Obsidian's secure
Installation
Method 1: Obsidian Community Plugins Directory
- Open Obsidian Settings > Community plugins.
- Turn off Restricted mode.
- Click Browse and search for SEOWebChecker SEO Audit.
- Click Install, then Enable.
Method 2: Manual Installation
- Download
manifest.json,main.js, andstyles.cssfrom the latest release. - Inside your Obsidian vault, navigate to
.obsidian/plugins/. - Create a new directory named
seowebchecker-seo-audit. - Copy
manifest.json,main.js, andstyles.cssinto that directory. - In Obsidian, go to Settings > Community plugins and enable SEOWebChecker SEO Audit.
Usage
1. Open the SEO Audit Sidebar
- Click the Gauge icon in the left ribbon, OR
- Open the Command Palette (
Ctrl+P/Cmd+P) and run:SEOWebChecker: Open SEO Audit Sidebar
2. Insert SEO Frontmatter Template
- In any Markdown note, run:
SEOWebChecker: Insert SEO Frontmatter Template - This inserts a clean, SEO-optimized YAML frontmatter header:
--- title: "Your Comprehensive Article Title" description: "A compelling 120-165 character summary describing the core value of this article." canonical: "https://example.com/blog/article-slug" focus_keyword: "primary target term" slug: "article-slug" ---
3. Review Diagnostics
- Use the sidebar tabs (Overview, Headings, Readability, Live URL) to review actionable recommendations and resolve warnings before publishing your post.
Official Links
- Platform: https://seowebchecker.com/
- Repository: https://github.com/jaiganesh6999/seowebchecker-seoaudit-sdk
- Issue Tracker: https://github.com/jaiganesh6999/seowebchecker-seoaudit-sdk/issues
License
MIT License. Copyright (c) 2026 SEOWebChecker.
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.