On-Page SEO Checker

Free, no signup. A concise five-item on-page memo first, with the full raw-HTML detector output available in Advanced.

General preserves the base report. A named profile adds its required-signal checks; unavailable schema guidance and pack weights stay visibly not evaluated.

Checks run from our server; we fetch the URL you enter and don't keep the results. Anonymous run-level outcome counters may be used for aggregate research; URLs, domains, IPs, and identifiers are never included, and no statistic is released below 100 runs.

Feedback
Report a bug

Found something broken in On Page Seo Checker? Let us know what happened — this goes straight to a private triage queue, not a public list.

What will be sent
 No tool inputs, uploads, pasted source, complete results, query parameters, or URL fragments are attached automatically. You can edit or remove the selected passage above. Browser and anti-abuse metadata is processed for spam prevention. 

Sample report

Illustrative example — deterministic raw-HTML findings, not a live site claim

For a 200 page with no title, one H1, a self-canonical, a missing meta description, and an image without alt text, the report would summarize:

Top 5 prioritized findings

2 errors · 1 warning · supporting passes and not-evaluated checks

Page title · No title element was found.
Meta description · No meta description was found.
Image alt text · One image needs review.
Primary heading · One H1 was observed.
Rendered-only checks · Not evaluated in raw-HTML mode.

How to use it

  1. Enter a public, crawlable page URL and choose Run report.
  2. Start on Simple: top 5 for the highest-priority memo.
  3. Open Advanced: all checks to see every supported detector, including passes and not-evaluated states.
  4. Verify important fixes in the rendered page and Search Console where appropriate.

What the results mean

  • Errors (red) are clear implementation defects or strong blockers supported by the response.
  • Warnings (orange) are likely issues that need context before changing the page.
  • Needs review (yellow) marks evidence that cannot support a pass or error verdict yet.
  • Information (blue) records useful evidence without calling it a defect.
  • Pass means that specific observable rule passed, not that the whole page is optimized.
  • Not evaluated means no verdict was possible and never counts as a pass.

How it works

The server retrieves the public response because browser cross-origin rules prevent direct inspection. The page context normalizes the final URL, status, headers, and raw HTML, then a deterministic detector registry runs supported technical and on-page checks. The Simple memo prioritizes the same results; it does not use a separate opaque score.

Features

  • Five-item prioritized memo plus complete detector output.
  • Checks across metadata, headings, canonicals, directives, links, images, and supported markup.
  • Hreflang cluster validation follows up to 500 declared URLs with at most six concurrent fetches.
  • Evidence-based pass, warning, error, information, and not-evaluated states.
  • Escaped output and no fabricated verdicts when evidence is unavailable.

Limitations

This checker does not render JavaScript, run Lighthouse, measure Core Web Vitals, assess accessibility, score writing quality, inspect backlinks, or predict rankings. Hreflang detail shown on the page and in coverage samples is bounded even when validation reaches the 500-URL ceiling. A fetch can also differ from Googlebot because it originates from this site's server infrastructure. Confirm rendered and index-level behavior with purpose-built tools.

Frequently asked questions

What does an on-page SEO checker analyze?

This checker analyzes signals available in the server-returned HTML and response metadata, including titles, descriptions, headings, canonicals, robots directives, links, images, and supported structured-data patterns.

Is a passing report a guarantee that the page will rank?

No. The report identifies observable implementation issues. Rankings also depend on relevance, content quality, competition, authority, internal linking, and signals this raw-HTML tool cannot measure.

Why does the report say not evaluated?

Not evaluated means the checker lacks the evidence or rendering capability needed for a responsible verdict. It is different from a pass and keeps unavailable checks from inflating the result.

Does the checker render JavaScript?

No. It analyzes the raw HTML response. Use a rendered-page tool when a JavaScript application changes metadata, headings, content, or links after load.

Which findings should I fix first?

Start with errors that can prevent crawling, indexing, or a useful search result, then address warnings that affect page meaning. The Simple tab prioritizes five findings using the same detector results shown in Advanced.

Next stepContent Gap Analyzer — look up the exact spec and expected values.

Feature requests for On Page Seo Checker

Upvote what you want most. New ideas can be submitted from the floating Feedback menu; requests appear here once approved, and the most-wanted rise to the top.

Loading…

➕ Request a feature

New requests are reviewed before they appear here.

Tentang alat

Gratis, tanpa pendaftaran. concise five-item pada-halaman memo pertama, dengan penuh mentah-HTML detector keluaran tersedia di Lanjutan.

Bagaimana ini berfungsi server retrieves publik respons karena browser cross-asal aturan prevent langsung inspeksi. halaman konteks normalizes akhir URL, status, header, dan mentah HTML, lalu deterministik detector registry berjalan supported teknis dan pada-halaman memeriksa. Simple memo prioritizes sama hasil; ini tidak menggunakan terpisah opaque score.

Simple: top 5 Lanjutan: semua memeriksa Ekspor audit bundel Bandingkan bundel Berubah halaman? Bandingkan dipilih Wayback tangkap dengan saat halaman.

Fitur

  • Publik halaman URL Jalankan laporan Halaman profile General mempertahankan dasar laporan. named profile menambahkan wajib-nya-sinyal memeriksa; tidak tersedia skema guidance dan pack weights stay visibly tidak dievaluasi.
  • Bagaimana untuk gunakan ini Masukkan publik, dapat dirayapi halaman URL dan pilih Jalankan laporan. Mulai pada Simple: top 5 untuk highest-prioritas memo. Buka Lanjutan: semua memeriksa untuk melihat setiap supported detector, termasuk passes dan tidak-dievaluasi keadaan. Verifikasi penting perbaikan di dirender halaman dan Search Console di mana tepat.
  • Tidak dievaluasi berarti pemeriksa tidak memiliki bukti atau perenderan capability diperlukan untuk responsible putusan. Ini adalah berbeda dari lulus dan mempertahankan tidak tersedia memeriksa dari inflating hasil.
  • Tidak. Ini analyzes mentah HTML respons. Gunakan dirender-halaman alat ketika JavaScript aplikasi perubahan metadata, headings, konten, atau tautan setelah muat.
  • Tidak. laporan mengidentifikasi dapat diamati implementasi masalah. Peringkat juga depend pada relevance, konten kualitas, competition, authority, internal linking, dan sinyal ini mentah-HTML alat tidak dapat ukur.

Cara kerja

Melakukan pemeriksa render JavaScript? Ini pemeriksa analyzes sinyal tersedia di server-dikembalikan HTML dan respons metadata, termasuk titles, descriptions, headings, canonical, robots direktif, tautan, images, dan supported structured-data pola. Home › Alat › Pada-Halaman SEO Pemeriksa Mengapa melakukan laporan say tidak dievaluasi?

Batasan

  • prioritized pada-halaman SEO laporan dari mentah HTML dan dapat diamati header respons.
  • Yang temuan seharusnya I perbaikan pertama?
  • Pada-Halaman SEO Pemeriksa
  • Adalah passing laporan jaminan yang halaman akan rank?

Pertanyaan umum

Home › Alat › Pada-Halaman SEO Pemeriksa

Mengapa melakukan laporan say tidak dievaluasi?

Laporan contoh Illustrative contoh — deterministik mentah-HTML temuan, tidak langsung situs klaim Untuk 200 halaman dengan tidak ada judul, satu H1, sendiri-canonical, hilang meta deskripsi, dan image tanpa alt teks, laporan akan summarize: Top 5 prioritized temuan 2 kesalahan · 1 peringatan · supporting passes dan tidak-dievaluasi memeriksa Halaman judul · Tidak ada judul element adalah ditemukan. Meta deskripsi · Tidak ada meta deskripsi adalah ditemukan. Image alt teks · Satu image needs tinjau. Utama heading · Satu H1 adalah teramati. Dirender-hanya memeriksa · Tidak dievaluasi di mentah-HTML mode.

Apa melakukan pada-halaman SEO pemeriksa analyze?

Mulai dengan kesalahan yang dapat prevent perayapan, pengindeksan, atau berguna pencarian hasil, lalu alamat peringatan yang affect halaman arti. Simple tab prioritizes five temuan menggunakan sama detector hasil ditampilkan di Lanjutan.

Batasan Ini pemeriksa tidak render JavaScript, jalankan Lighthouse, ukur Core Web Vitals, assess accessibility, score writing kualitas, periksa backlinks, atau predict peringkat. Hreflang detail ditampilkan pada halaman dan di cakupan sampel adalah dibatasi even ketika validasi reaches 500-URL ceiling. ambil dapat juga berbeda dari Googlebot karena ini originates dari situs's server infrastructure. Konfirmasi dirender dan indeks-tingkat perilaku dengan tujuan-dibangun alat.

Arti hasil Kesalahan (red) adalah jelas implementasi defects atau strong penghambat supported oleh respons. Peringatan (orange) adalah kemungkinan masalah yang perlu konteks sebelum berubah halaman. Needs tinjau (yellow) menandai bukti yang tidak dapat mendukung lulus atau kesalahan putusan namun. Information (blue) catatan berguna bukti tanpa calling ini cacat. Lulus berarti yang spesifik dapat diamati aturan passed, tidak yang seluruh halaman adalah optimized. Tidak dievaluasi berarti tidak ada putusan adalah mungkin dan tidak pernah counts sebagai lulus.

Fitur Five-item prioritized memo plus lengkap detector keluaran. Memeriksa di seluruh metadata, headings, canonical, direktif, tautan, images, dan supported markup. Hreflang klaster validasi mengikuti up untuk 500 dinyatakan URLs dengan di paling six concurrent mengambil. Bukti-berdasarkan lulus, peringatan, kesalahan, information, dan tidak-dievaluasi keadaan. Escaped keluaran dan tidak ada fabricated verdicts ketika bukti tidak tersedia.