SECURITY
CHECK 1 · Core
Active and Forced HTTPS
Checks that the website loads over HTTPS, redirects from HTTP and does not keep insecure versions active.
Technical directory
Checks to review signals before they become problems
The modular AISEO checks let you verify specific pieces of your infrastructure. The perfect complement to understand specific failures or prepare your site before a full audit.
SIGNAL_MAP
READING BASE...
signals.exe
[1] Technical base OK
[2] Crawling & semantics ACTIVE
[3] IA preparation VALIDATING...
> LAYER READING ACTIVE
> Reviewing HTTPS, HTTP states and stability.
AISEO Modules
A check tells you what it sees. The AISEO system tells you what it means.
These checks function as independent sensors. You can use them to confirm if your robots.txt file is blocking routes, if your HTTPS is correctly forced or if your content is accessible without depending on JavaScript.
However, to understand how each signal affects ranking, AI extraction and CertiScore, you need the full context of the AISEO audit.
Technical directory
Checks directory
Browse the 30 technical checks organized by their function within the AISEO validation ecosystem.
CRAWLABILITY
CHECK 2 · Core
Status Codes & Navigation
An incorrect HTTP code prevents indexing and insufficient internal links hinder crawling. This check evaluates both aspects in a single pass.
CRAWLING
CHECK 3 · Core
Functional Robots.txt
The robots.txt file guides crawlers on which areas they can crawl. A badly written rule can block critical sections or even leave a full website out of crawling.
CRAWLING
CHECK 4 · Core
Coherent Meta Robots
Avoids contradictions between HTTP headers and meta tags that confuse search engines, crawlers and AI systems.
SECURITY
CHECK 5 · Core
No Mixed Content
Checks that an HTTPS page does not load images, scripts, styles or internal resources through insecure HTTP.
CRAWLING
CHECK 6 · Core
Detectable 404 Page
Checks that nonexistent URLs return a real 404 status and not an apparently valid page with error content.
CRAWLING
CHECK 7 · Core
Valid XML Sitemap
Provides a reliable list of URLs. If it contains errors, bots lose trust in the domain signal.
CRAWLING
CHECK 8 · Core
Self-Referencing Canonical
Avoids duplicates and consolidates signals on the preferred URL.
SEMANTICS
CHECK 9 · Core
Metadata (Title + Description)
They are the first context vector for search engines and AI models.
SEMANTICS
CHECK 10 · Core
Unique Identifiable H1
Defines the main topic. Multiple H1 tags break semantic hierarchy.
CRAWLING
CHECK 11 · Core
Content Accessible Without JavaScript
If the content depends on JavaScript, many bots will not see it.
SEMANTICS
CHECK 12 · Core
Native UTF-8 Encoding
Prevents character errors that damage semantic extraction.
PERFORMANCE
CHECK 13 · Core
Technical Performance
Evaluate whether the page loads smoothly, stably, and efficiently before delving into advanced user experience metrics.
SEMANTICS
CHECK 14 · Core
Image Alt Text
Ensures important images have useful alternative text without decorative noise.
SECURITY
CHECK 15 · Core
Security Headers
HSTS, X-Frame and other headers improve the technical reputation and security of the domain.
SCHEMA
CHECK 16 · Structural signals
Breadcrumbs Schema
Clarifies the position of the URL within the site architecture for users, search engines and AI systems.
AI READY
CHECK 17 · AI Strategy
Snippet Eligibility
Even if your page is indexed, anti-snippet directives exclude it from Google rich results and generative AI citations. In the era of AI-assisted search, not being snippet-eligible means being invisible.
SEMANTICS
CHECK 18 · Structural signals
Heading Hierarchy
Checks that H1, H2, H3 and following levels create a coherent reading structure for users, search engines and AI systems.
SEMANTICS
CHECK 19 · Structural signals
Friendly URLs
Checks whether the URL communicates meaning before the page loads and avoids unnecessary technical noise.
SEMANTICS
CHECK 20 · Structural signals
Lang and Hreflang
Prevents language confusion and helps users, search engines and AI systems reach the correct version.
Mobile
CHECK 21 · Structural signals
Mobile-First Experience and Mobile-Desktop Parity
Check that the page has a proper mobile base and that the mobile version retains the essential desktop content.
PERFORMANCE
CHECK 22 · Structural signals
HTML Image Optimization
Checks whether image HTML helps performance, stability and content priority instead of slowing the page down.
CRAWLING
CHECK 23 · Structural signals
Crawl Depth
Checks whether important pages are close enough to the home page and not buried inside a deep architecture.
CRAWLING
CHECK 24 · Structural signals
Healthy Redirects
Checks whether redirects are direct, intentional and technically clean.
PERFORMANCE
CHECK 25 · AI Advanced
Core Web Vitals
Evaluates LCP, INP and CLS as signals of real performance and usability.
AI READY
CHECK 26 · AI Advanced
Site Identity (JSON-LD)
Helps search engines and AI systems understand who owns, publishes or represents the website.
AI READY
CHECK 27 · AI Advanced
Content Readability (Flesch)
Checks whether text density, sentence length and clarity support better reading and extraction.
AI READY
CHECK 28 · AI Advanced
Chunkable Structure (RAG)
Evaluates whether the structure helps RAG systems retrieve useful fragments without losing context.
AI READY
CHECK 29 · AI Advanced
Transparency Signals (E-E-A-T)
Checks whether users, search engines and AI systems can understand who is behind the content and why it deserves trust.
AI READY
CHECK 30 · AI Advanced
Detectable Useful Content
Detects whether the page contributes real value or only fills space with decorative, generic or redundant text.
Usage roles
Checks by role
Modular checks allow each professional to focus on the technical area they are responsible for solving.
Web Developers
Verify DOM cleanliness, content exposed without JS, HTTPS, redirects and security headers during production deployment.
SEO Consultants
Use crawling, canonical, robots, sitemap and metadata checks to detect specific incidents without launching a full audit.
Content Managers
Evaluate headings, readability, detectable usefulness and chunkable structure so that content is more interpretable by search engines and AI systems.
Frequently asked questions about checks
We clarify how to use these modules inside and outside the system.
Do these checks replace the full AISEO audit?
No. Each check reviews a specific signal. The complete audit crosses all signals, applies weights, interprets impact and calculates the CertiScore.
Why are they separated into individual pages?
Because each signal needs its own explanation, examples, frequent errors and a clear improvement path. Separating them improves maintenance, SEO and technical understanding.
Do individual pages use a common template?
Yes. The structure is based on a reusable template to avoid duplicating HTML, CSS and visual logic in the 30 checks.