Skip to main content
Archived

SEO Report for https://gamebai1.app

Your general SEO Checkup Score

SEO Score71/100
Average SEO score of top 100 sites: 75%This value indicates the average SEO score of the top 100 most visited websites in the US (in the past 12 months)
AI Visibility36/100
AI visibility score reflects brand reach in AI

Your site scored 71/100, below the 75 average for top sites. We found 13 issues to fix, and clearing them is how you move up. And an AI Visibility Score of 36/100 means ChatGPT, Gemini and Perplexity mention your brand only occasionally, which is ground your competitors are leaving open.

13 Failed
3 Warnings
47 Passed

Want to fix these issues and track your progress?

Issues to fix

HIGH
To improve the website experience for your visitors, it is recommended to eliminate any render-blocking resources on this webpage.
Details
HIGH
H1 and H2 tags ensure better search engine visibility and ranking by providing structure and hierarchy to the content, improving readability, and providing opportunities for keyword optimization.
Details
HIGH
Add a meta description tag to provide a brief and informative summary of the page's content for search engines.
Details
HIGH
To ensure that Search Engines can accurately identify the topic of this webpage, it is important to include the most common keywords in the title tag, meta description, and heading tags.
Details
HIGH
Add a sitemap file to help search engine crawlers index content more thoroughly and quickly.
Details
MEDIUM
Avoid using distorted images, as they can have a negative impact on the user experience.
Details
MEDIUM
Consider using structured data in your webpage as it can help search engines gain a better understanding of your content.
Details
MEDIUM
Add a Google Analytics script to this website to help in diagnosing potential SEO issues by monitoring site visitors and traffic sources.
Details
MEDIUM
Using social media meta tags can improve the appearance and content of shared links on social media platforms, potentially increasing click-through rates and engagement with the page.
Details
LOW
Keep in mind that the NOINDEX meta tag instructs search engines not to index a webpage. Please verify if this is the intended behavior, as the webpage will not appear in search engine results.
Details
LOW
Without an SPF record, spammers can easily spoof emails from this domain, potentially leading to compromised email security and deliverability issues.
Details
LOW
Consider adding the Strict-Transport-Security header to your webpage to ensure that web traffic is encrypted over HTTPS, mitigating the risk of man-in-the-middle attacks and other security threats.
Details

AI Insights

Score:0
Failed:0
Warnings:0
Passed:5
Domain Business Context
Understanding the business context of a domain can help you create content that is more relevant to your target audience and differentiate your website from competitors.

What is this domain about

A basic WordPress site with a default starter post and minimal published content.

Industry Niche

General WordPress Publishing

Target Audience

General visitors or site owners testing a newly launched website.

This test will check the business context of the domain associated with the analyzed webpage. The business context includes the domain's description, target audience and industry niche (if applicable). Understanding the business context of a domain can help you create content that is more relevant to your target audience and differentiate your website from competitors.
LLM Visibility Checker
LLM Visibility Checker

Track your brand across ChatGPT, Gemini and Claude

Get an AI Presence Score, see which of your pages get cited, and follow how you compare with competitors over time.

How visible your brand is to AI engines
Content Strengths and Weaknesses

This webpage is extremely minimal and appears to be a default WordPress installation with one starter post. It has clear basic structure, but very little depth, originality, or trust-building content.

Content Strengths

  • Clear Basic Structure
  • Recent Publish Date
  • Localized Content

Content Weaknesses

  • Very Limited Depth
  • No Author Details
  • Weak Engagement
This test will analyze the content of the webpage to identify its strengths and weaknesses. The analysis includes factors such as keyword usage, readability, originality, and relevance to the target audience. By understanding the strengths and weaknesses of your content, you can make informed decisions about how to improve it and better meet the needs of your audience.
Content Trust
24%
Topical Relevance90%
Subject Expertise10%
Credibility20%

This webpage has low trust signals because it mainly shows a default starter post with almost no supporting information. The page includes a dated post and site branding, but it lacks visible author details, policy pages, contact information, or third-party validation.

This test will evaluate the trustworthiness of the content on the webpage. It assesses factors such as the credibility of sources, accuracy of information, and overall reliability. A high level of content trust can enhance your website's reputation and improve its ranking in search engine results.
Visual SEO Analysis
Visual SEO Analysis

Find out if your page design converts the visitors you earn

We score six things that decide whether a visitor stays and acts, from the first screen to the path to action, and rank every fix by effort and impact.

How your page's design and UX affect conversions
Content Freshness
72%

The page appears recently published and current at the page level, with a visible post date in late 2026 and a 2026 copyright notice. However, the freshness is mostly boilerplate-based rather than driven by regularly updated core content.

Positive Signals

  • Recent post date
  • 2026 copyright notice

Staleness Signals

  • Default starter content
  • No ongoing updates
This test will check the freshness of the content on the webpage. It evaluates how recently the content was created or updated, and whether it remains relevant to current trends and user interests. Fresh content can attract more visitors and improve your website's ranking in search engine results.
Content Opportunities

The site has substantial room to grow from a default starter page into a useful, trustable content destination. The biggest opportunities are to replace generic content with original articles, add supporting trust pages, and build a clearer content structure around a defined audience and topic.

Quick Wins

  • •Replace the default first post with a real article on the site’s main topic.
  • •Create and link an About page that explains who runs the website.
  • •Add visible footer links to Privacy Policy and Contact pages.
This test will identify potential content opportunities for the webpage. It analyzes the current content landscape, identifies gaps in coverage, and suggests topics or keywords that could be targeted to attract more visitors and improve search engine rankings.

Common SEO issues

Score:43
Failed:7
Warnings:1
Passed:11
Meta Title Test
100% of top 100 sites passed
This webpage is using a title tag with a length of 12 characters. While there's no target number of characters, titles should be descriptive and concise. Using a title tag with less than 20 characters is a missed opportunity since it can be difficult to fit all your targeted keywords in such a short text.
We recommend using a title with a length between 20 - 60 characters in order to fit Google Search results that have a 600-pixel limit.
Text: gamebai1.app
Length: 12 characters
The meta title is an HTML element that defines a page's title, displayed in search engine results, browser tabs, and bookmark lists. A concise, keyword-relevant title is a strong on-page ranking signal and a major driver of organic click-through rate. AI answer engines and LLM-driven search experiences also rely on the title to identify, summarize, and cite the page in generative results.
Meta Description Test
92% of top 100 sites passed
This webpage is not using a meta description tag! You should include this tag in order to provide a brief description of your page which can be used by search engines. Well-written and inviting meta descriptions may also help click-through rates to your site in search engine results.

Meta Description Test

How to pass this test?

The meta description is a short summary of the page that often appears beneath the title in search results and on social previews. Fixing this issue means adding a unique, accurate, action-oriented description to each page so search engines and link unfurlers have a trusted snippet to surface. AI answer engines and social platforms also use the meta description as a high-trust summary when generating previews, citations, and shareable snippets, which makes the same fix valuable for AEO visibility.

Example

<head>
  <meta name="description" content="Compare lightweight marathon running shoes from leading brands. Specs, weight, drop, and verified runner reviews to help you choose your next pair.">
</head>

Where to make the change

  • Raw HTML: add a single <meta name="description"> tag inside the <head>. The element has no closing tag in HTML5.
  • WordPress: install a dedicated SEO plugin and fill the Meta description field on each post and page. Most plugins show a live SERP preview as you type.
  • Shopify: open the page, product, or collection editor, expand Search engine listing preview, and edit the Description field.
  • Wix or Squarespace: open the page settings, locate the SEO panel, and update the Description field.
  • Headless or framework sites: emit the meta tag from the framework's metadata API so it is present in the initial HTML response and reachable without running JavaScript.

Common causes and how to resolve them

  • Tag is missing: add a <meta name="description"> inside the <head>. CMS themes sometimes omit it from custom templates.
  • Empty content attribute: the tag exists but its content value is blank. Populate it with a unique, page-specific summary.
  • Duplicate descriptions across pages: the same boilerplate is applied site-wide, giving Google no reason to differentiate listings. Write a unique description for every important page; even templated product or category pages benefit from variant-specific copy.
  • Unescaped quotes in the value: a stray double quote inside the content attribute breaks the tag silently. Use single quotes or the HTML entity &quot; inside the value.
  • Description set only by client-side JavaScript: render the meta tag in the initial HTML response so search engines and social link unfurlers can read it without executing scripts.

Best practices

  • Length: aim for roughly 150 to 160 characters on desktop and about 120 on mobile. Front-load the most important message so it survives truncation on smaller screens.
  • Include the primary keyword: Google bolds matched query terms in the snippet, which improves visibility even though the description itself is not a direct ranking factor.
  • Use active, action-oriented language: tell the user what they will learn, find, or do on the page. Active verbs consistently outperform passive summaries on click-through rate.
  • One unique description per page: reuse is a wasted opportunity. Distinct descriptions help users choose your listing and help search engines understand which page is the best match for a query.
  • Expect occasional rewrites: Google sometimes ignores the meta description and generates a snippet from on-page content if it judges that more relevant for a given query. Strong on-page copy keeps both versions effective.
The meta description is an HTML tag that provides a short summary of a page's content, often shown beneath the title in search results. While not a direct ranking factor, an accurate and inviting description significantly improves click-through rate from organic listings. AI answer engines and social platforms also use it as a trusted summary when generating previews, citations and shareable snippets.
Google Search Results Preview Test
Desktop version
https://gamebai1.app/gamebai1.app
Mobile version
https://gamebai1.app/gamebai1.app
A simulated preview of how the page may appear in Google search results, combining the title, URL, and meta description as Google typically renders them. Useful for spotting truncated text, weak phrasing, or missing elements before publishing, since the snippet directly influences whether searchers click through.
Social Media Meta Tags Test
89% of top 100 sites passed
This webpage is not using social media meta tags! While this type of meta tags don't affect what people see when they visit the webpage, they exist to provide information about it to search engines and social media platforms.

Social Media Meta Tags Test

How to pass this test?

Open Graph and Twitter Card meta tags tell social platforms, link unfurlers, and AI crawlers how to display the page when its URL is shared. Adding the right tags produces richer previews with the intended title, description, and image, which lifts click-through on social channels and gives answer engines a structured summary to work with when citing the page.

Example

<head>
  <meta property="og:title" content="Lightweight Marathon Running Shoes">
  <meta property="og:description" content="Compare specs, weight, and runner reviews.">
  <meta property="og:image" content="https://example.com/images/og-shoes.jpg">
  <meta property="og:url" content="https://example.com/shoes/marathon">
  <meta property="og:type" content="article">
  <meta name="twitter:card" content="summary_large_image">
</head>

Where to make the change

  • Raw HTML: add the meta tags directly to the <head>. Open Graph properties use property= while Twitter Card properties use name=.
  • WordPress: a dedicated SEO plugin will populate Open Graph and Twitter Card tags from the post's title, excerpt, and featured image. Override per-post when the auto-derived value is weak.
  • Shopify: most modern themes emit Open Graph tags automatically. If yours does not, edit theme.liquid to add the tags inside the <head> using product or page metadata.
  • Wix or Squarespace: open the page settings and use the social sharing image and description fields. Both platforms render the corresponding meta tags on save.
  • Headless or framework sites: emit Open Graph and Twitter Card tags from the framework's metadata API alongside the title and meta description.

Common causes and how to resolve them

  • No social meta tags at all: add at minimum og:title, og:description, og:image, and og:url. These are the four properties most platforms rely on.
  • Missing or relative og:image URL: social platforms require an absolute, publicly reachable image URL. Use a full https:// URL, not a relative path.
  • Image too small or wrong aspect ratio: aim for at least 1200 x 630 pixels so the preview renders crisply on Facebook, LinkedIn, and X without awkward cropping.
  • Stale preview cached by the platform: after fixing the tags, use the platform's debugger (Facebook Sharing Debugger, X Cards Validator, LinkedIn Post Inspector) to invalidate the cache and re-scrape the page.

Best practices

  • Use absolute URLs everywhere: og:url and og:image must be fully qualified. Relative paths break previews on most platforms.
  • Pick a dedicated social image: a single hero image at 1200 x 630 with the page's main visual covers Facebook, LinkedIn, X (with summary_large_image), and most other platforms in one shot.
  • Set a sensible og:type: use article for blog posts, website for landing pages, and product for e-commerce items. The type affects how some platforms render the preview.
  • Add Twitter-specific tags only when they differ: X falls back to Open Graph when Twitter Card tags are absent, so duplicate them only when you genuinely want a different title, image, or card type.
Open Graph and Twitter Card meta tags tell social platforms and link unfurlers how to display a page when its URL is shared. Well-formed tags produce richer previews with the intended title, description, and image, which improves click-through on social channels. They also serve as a structured signal that AI crawlers and answer engines can use when summarizing the page.
Most Common Keywords Test
There is likely no optimal keyword density (search engine algorithms have evolved beyond keyword density metrics as a significant ranking factor). It can be useful, however, to note which keywords appear most often on your page and if they reflect the intended topic of your page. More importantly, the keywords on your page should appear within natural sounding and grammatically correct copy.
2chào
2người
1chuyển
1dung
1tháng
A frequency analysis of the most repeated words and phrases in the page's visible content. Useful for getting a quick sense of which topics search engines are likely to associate with the page, and for spotting cases where the actual content drifts from the intended subject.
Keywords Usage Test
48% of top 100 sites passed
The most common keywords of this webpage are not distributed across the important HTML tags! Primary keywords should appear in title tag, meta description and heading tags to help Search Engines to properly identify the topic of this webpage.
Keyword
Title tag
Meta description
Headings
chào
người
chuyển
dung
tháng
Cross-checks whether the most frequently used keywords on the page also appear in the title and meta description. Alignment between body content and metadata helps search engines confirm the page's topic and reinforces relevance for those terms.
Keywords Cloud Test
chuyển
chào
copyright
dung
dụng
flatsome
người
theme
tháng
tiên
viết
wordpress
A visual word cloud of the page's content, with more frequent terms shown in larger text. Provides a quick at-a-glance view of which words dominate the page, helping confirm that the visible content reflects the intended topic.
Related Keywords Test
Related Keywords

See which keywords rank your URL in Google’s top 20

Get key keyword metrics like average position, search volume, CPC, and more.

A list of search queries for which the page already appears in the top organic results. Highlights the topical territory the page is winning in search and can surface unexpected terms that present new content or optimization opportunities.
Competitor Domains Test
Competitor Domains

Understand your competitors' SEO and backlink profile

Get related competitors and their domain authority score in relation to your domain.

Identifies up to ten domains that compete for similar organic search results, ranked by overall domain authority based on the volume and quality of their backlink profiles. Useful for benchmarking the competitive landscape and prioritizing which sites to study for content and link-building strategy.
Heading Tags Test
62% of top 100 sites passed
This webpage does not contain H1 headings! H1 headings help indicate the important topics of your page to search engines. While less important than good meta-titles and descriptions, H1 headings may still help define the topic of your page to search engines.

Heading Tags Test

How to pass this test?

The H1 and H2 tags give search engines and assistive technology a clean outline of the page's topics. Fixing this issue means adding a single descriptive H1 and a logical hierarchy of H2 sub-sections so the page's structure is unambiguous to both users and machines. AI answer engines also use heading structure to segment content into discrete passages they can quote or summarize, so a clean hierarchy directly helps the page get picked up in generative results.

Example

<body>
  <h1>Lightweight Running Shoes for Marathons</h1>
  <h2>What to look for in a marathon shoe</h2>
  <h2>Top picks for 2026</h2>
  <h2>How we tested</h2>
</body>

Where to make the change

  • Raw HTML: add a single <h1> near the top of the page's main content, then use <h2> for major sections and <h3> for subsections under those.
  • WordPress: in the block editor, set the post title's heading level to H1 (themes usually do this automatically) and use the Heading block for in-body H2 and H3 sections.
  • Shopify: the product or page title field renders as an H1 in most themes. Use the rich-text editor to add H2 and H3 headings inside the body.
  • Wix or Squarespace: use the heading style picker in the block editor to assign H1, H2, and H3 levels rather than just changing font size.

Common causes and how to resolve them

  • No H1 on the page: add a single <h1> that names the page's primary topic. Many themes either skip the H1 or render the site logo as one.
  • Multiple H1s: while modern HTML allows multiple H1s, most SEO tools still flag them. Pick the most important one and demote the others to H2.
  • Headings used for visual styling only: bold or large text styled to look like a heading does not help search engines or screen readers. Use the actual heading tag and style it with CSS.
  • Hierarchy skips levels: jumping from H1 directly to H3 confuses assistive technology. Keep the order H1 then H2 then H3 without gaps.

Best practices

  • One H1 per page: reserve it for the page's main subject; treat it as the in-page equivalent of the title.
  • Make headings descriptive: each heading should make sense out of context. "How we tested" is better than "Methodology" alone if the page is a product review.
  • Include keywords naturally: H1 and H2 are mid-strength ranking signals. Use the focus keyword in the H1 and supporting terms in H2s when it reads naturally.
  • Outline the page from headings alone: if you can read just the H1 and H2s and understand what the page is about, the structure is doing its job.
Inspects the page for H1 and H2 heading tags and reports their structure. Headings give both users and search engines a clear outline of the page's topics, with the H1 acting as the primary subject and H2s framing major sections. A clean heading hierarchy also helps AI answer engines segment the content into discrete passages they can quote or summarize.
Robots.txt Test
99% of top 100 sites passed
This website is using a robots.txt file.
https://gamebai1.app/robots.txt
Verifies whether the site exposes a robots.txt file at the root domain. This file is the first resource most crawlers request, telling search engines and other bots which paths they may or may not access. It is also the standard mechanism for allowing or blocking modern AI crawlers used by training pipelines and answer engines.
Sitemap Test
83% of top 100 sites passed
This website lacks a sitemap file! Sitemaps can help robots index your content more thoroughly and quickly. Read more on Google's guidelines for implementing the sitemap protocol.

Sitemap Test

How to pass this test?

An XML sitemap gives search engines and AI crawlers an explicit, machine-readable list of the URLs you want indexed, along with metadata such as last-modified dates. Fixing this issue means generating a valid sitemap, publishing it at a stable URL, and pointing crawlers to it via robots.txt and Search Console. This is especially important for large sites, sites with weak internal linking, or sites where new content needs to be discovered quickly.

Example

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/</loc>
    <lastmod>2026-04-15</lastmod>
  </url>
  <url>
    <loc>https://example.com/blog/getting-started</loc>
    <lastmod>2026-03-22</lastmod>
  </url>
</urlset>

Where to make the change

  • Raw HTML or static site: generate the XML at build time and publish it at /sitemap.xml. Many static-site generators have a built-in sitemap option.
  • WordPress: a dedicated SEO plugin will generate and update the sitemap automatically, typically at /sitemap_index.xml.
  • Shopify: Shopify generates /sitemap.xml automatically and updates it as products and collections change.
  • Wix or Squarespace: both platforms generate the sitemap automatically and serve it at the standard root path.
  • Headless or framework sites: use the framework's built-in sitemap module (for example next-sitemap for Next.js or the @astrojs/sitemap integration) so the file is regenerated on every build.

Common causes and how to resolve them

  • No sitemap published: generate one and publish it at the site root. Reference it from robots.txt with a Sitemap: line.
  • Sitemap lists URLs that 404 or redirect: stale entries waste crawl budget and trigger Search Console warnings. Regenerate the sitemap from current published URLs only.
  • Mixed canonical and non-canonical URLs: the sitemap should list canonical URLs only. Listing both http and https, or trailing-slash variants, splits crawl signals.
  • Sitemap exceeds size limits: a single sitemap may contain at most 50,000 URLs and 50 MB uncompressed. Split larger sites into multiple sitemaps and reference them from a sitemap index file.

Best practices

  • Submit to Search Console: add the sitemap URL in Google Search Console (and Bing Webmaster Tools) so the platform tracks coverage and surfaces errors.
  • Keep lastmod accurate: Google uses lastmod as a hint when prioritizing crawls. Update it whenever the page content meaningfully changes; do not bump it on every build.
  • Exclude noindex and disallowed URLs: the sitemap should describe what you want indexed. Listing pages that are blocked from crawling sends mixed signals.
  • Use sitemap index files for multi-sitemap setups: a sitemap index aggregates child sitemaps (for example one per content type) and is the single URL you submit to search engines.
Looks for an XML sitemap on the site and reports whether one is published. Sitemaps give search engines an explicit, machine-readable list of the URLs you want crawled, along with metadata such as last-modified dates, which speeds up discovery of new and updated pages. They are especially useful for large sites or those with weak internal linking.
Image Alt Test
78% of top 100 sites passed
All "img" tags from this webpage have the required "alt" attribute.
Inspects whether images on the page include descriptive alt attributes. Alt text provides accessibility for screen readers, a fallback when images fail to load, and a textual signal that helps search engines understand image content. It also improves how AI crawlers and image search tools interpret and surface the visuals.
Responsive Image Test
29% of top 100 sites passed
All images in this webpage are properly sized for different users' viewports.
Compares the natural dimensions of each image to the size at which it is actually rendered in the user's viewport. Serving images significantly larger than needed wastes bandwidth, slows page load, and forces the browser to scale assets unnecessarily, all of which hurt performance and user experience.
Image Aspect Ratio Test
75% of top 100 sites passed
Not all image display dimensions match the natural aspect ratio! Fix aspect ratio issues to avoid distorted images on this website!

Image Aspect Ratio Test

How to pass this test?

This test fails when one or more images are rendered at an aspect ratio meaningfully different from the source file's native ratio, producing stretched or squashed visuals. Fixing this issue means either using width and height attributes that match the file's real dimensions or replacing the source with a correctly proportioned crop.

Example

<!-- Source file is 1600 x 900 (16:9). Set matching attributes: -->
<img src="/images/marathon-1600.jpg"
     alt="Marathon runners at sunrise"
     width="1600" height="900"
     style="max-width: 100%; height: auto;">

Where to make the change

  • Raw HTML and CSS: set the width and height attributes to the source file's native dimensions. Use CSS height: auto when scaling responsively so the browser preserves the ratio.
  • WordPress: when inserting an image via the block editor, choose the image's intended size rather than overriding dimensions in custom CSS.
  • Shopify, Wix, or Squarespace: use the platform's built-in image cropper so the displayed crop matches the source file you upload.
  • Headless or framework sites: components like next/image require both width and height, which prevents distortion when the layout scales.

Common causes and how to resolve them

  • Hard-coded width and height that do not match the file: recompute them from the source dimensions or remove them and rely on the file's intrinsic ratio.
  • Container has a fixed height that crops the image: use CSS object-fit: cover if cropping is intentional, or change the container so the image keeps its natural ratio.
  • Wrong source file uploaded: swap in a correctly proportioned crop rather than stretching the wrong file in CSS.

Best practices

  • Always set both width and height: the browser uses these to reserve space and avoid layout shift before the image loads, which helps CLS.
  • Use object-fit when cropping is intentional: cover fills the container without distortion; contain letterboxes to preserve the full image.
  • Standardize on a few aspect ratios: picking one or two ratios per template makes it easier to crop assets consistently and avoid one-off distortions.
Compares each image's natural aspect ratio against the ratio at which it is displayed on the page. Significant mismatches result in stretched or squashed visuals that look unprofessional and degrade the user experience.
Deprecated HTML Tags Test
94% of top 100 sites passed
This webpage does not use HTML deprecated tags.
Scans the markup for HTML elements that are no longer part of the modern HTML specification. Deprecated tags may still render today, but browsers can drop support at any time, leading to broken layouts and rendering inconsistencies. Replacing them with current standards keeps the page resilient and easier to maintain.
Google Analytics Test
72% of top 100 sites passed
A Google Analytics script is not detected on this page. While there are several tools available to monitor your site's visitors and traffic sources, Google Analytics is a free, commonly recommended program to help diagnose potential SEO issues.

Google Analytics Test

How to pass this test?

Google Analytics 4 is a free measurement platform that records visitor behavior, traffic sources, and conversion data. Installing it does not directly affect rankings, but the data it produces is essential for measuring SEO performance, identifying high-value pages, and prioritizing future optimization work. Fixing this issue means installing the GA4 tag site-wide and confirming events appear in your reports.

Example

<!-- Place inside <head> on every page -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-XXXXXXXXXX');
</script>

Where to make the change

  • Raw HTML: paste the GA4 snippet into the <head> of every page. A shared layout file is the cleanest place.
  • WordPress: use a site-kit or analytics plugin, or paste the snippet into your theme's header file. Avoid duplicating the tag across multiple plugins.
  • Shopify: add the GA4 measurement ID under Online Store, Preferences, Google Analytics, or install the official Google channel app.
  • Wix or Squarespace: both platforms offer a GA4 measurement ID field in their analytics settings panel.
  • Headless or framework sites: install via Google Tag Manager or use the framework's analytics integration so the tag fires on every route change.

Common causes and how to resolve them

  • Tag not installed at all: install GA4 using the snippet above or the platform-specific path.
  • Universal Analytics tag still in place: Universal Analytics stopped processing data on July 1, 2024. Replace any UA tag (UA-...) with a GA4 measurement ID (G-...).
  • Tag fires only on the homepage: ensure the snippet is in a shared template loaded by every page, not pasted into one post.
  • Cookie banner blocks the tag before consent: integrate Consent Mode v2 so GA4 receives anonymized signals before consent and full data after.
  • Tag duplicated: two snippets on the same page double-count sessions. Audit with the Tag Assistant browser extension and remove duplicates.

Best practices

  • Verify with real-time reports: after installing, open GA4's Realtime view and load the site to confirm events arrive.
  • Use Google Tag Manager: for any site beyond the simplest, GTM gives you a single place to manage analytics, conversion tags, and third-party scripts without code changes.
  • Configure key events: mark conversions (purchase, lead, signup) as key events so reports highlight what matters for SEO ROI.
  • Link to Search Console: connecting GA4 to Search Console surfaces organic queries alongside on-site behavior in the same reports.
Detects whether the page is instrumented with Google Analytics tracking code. Analytics is not an SEO ranking factor, but having reliable traffic and behavior data is essential for measuring the impact of SEO work and identifying opportunities for improvement.
Favicon Test
100% of top 100 sites passed
favicon
This website appears to have a favicon.
Verifies whether the site declares a favicon and that it loads correctly. Favicons appear in browser tabs, bookmarks, and increasingly in search engine result pages, where they reinforce brand recognition and make a listing easier to spot at a glance.
Backlinks Test
Backlinks

Get a full and detailed list of your backlinks

See every website linking to yours, along with detailed backlink data.

Surfaces the external pages that link to the analyzed URL. Backlinks from authoritative, topically relevant sites remain one of the strongest off-page ranking signals, while a profile dominated by low-quality or spammy links can attract algorithmic penalties. Reviewing the inbound link mix helps identify both link-building wins and toxic links worth disavowing.
JS Error Test
83% of top 100 sites passed
There are no severe JavaScript errors on this webpage.
Inspects the page for JavaScript runtime errors that occur as it loads. Unhandled errors can break interactive features, leave content unrendered, and signal poor code quality, all of which hurt the user experience that search engines factor into rankings.
Console Errors Test
27% of top 100 sites passed
This webpage doesn't have any warnings or errors caught by the Chrome DevTools Console.
Reviews the browser console for warnings and errors emitted while the page loads. Console messages often expose underlying issues such as failed network requests, deprecated APIs, or security warnings that can quietly degrade the experience even when the page appears to work.
Charset Declaration Test
96% of top 100 sites passed
This webpage has a character encoding declaration.
Content-Type: text/html; charset=UTF-8
Checks whether the page declares a character encoding such as UTF-8. Without an explicit charset declaration, browsers must guess the encoding, which can lead to garbled symbols, broken accented characters, and inconsistent rendering across devices. UTF-8 is the modern standard recommended by Google.

Speed optimizations

Score:89
Failed:1
Warnings:1
Passed:18
HTML Page Size Test
23% of top 100 sites passed
The size of this webpage's HTML is 9.43 Kb and is under the average webpage's HTML size of 33 Kb. Faster loading websites result in a better user experience, higher conversion rates, and generally better search engine rankings.
Measures the size of the raw HTML document, excluding images and external CSS or JavaScript. Bloated HTML increases time to first byte and parsing time, slowing down rendering on mobile networks and lower-powered devices. Trimming inline styles, redundant markup, and oversized inline data keeps initial load fast.
DOM Size Test
56% of top 100 sites passed
The Document Object Model (DOM) of this webpage has 88 nodes which is less than the recommended value of 1,500 nodes.
Measures the size and depth of the page's Document Object Model, the tree of nodes the browser builds from the HTML. Very large DOMs increase memory usage, lengthen style and layout calculations, and slow down rendering, particularly on mobile devices. Keeping the DOM lean improves both load time and runtime responsiveness.
HTML Compression/GZIP Test
99% of top 100 sites passed
This webpage is successfully compressed using zstd compression on your code. The HTML code is compressed from 36.02 Kb to 9.43 Kb (74% size savings). This helps ensure a faster loading webpage and improved user experience.
Verifies whether the server delivers the HTML using a compression algorithm such as Gzip or Brotli. Compressed responses dramatically reduce transfer size with negligible decompression cost, translating directly into faster page loads, especially on slower connections.
Site Loading Speed Test
71% of top 100 sites passed
The loading time of this webpage (measured from N. Virginia, US) is around 1.73 seconds and this is under the average loading speed which is 5 seconds.
Related Keywords

Accurate historical loading speed monitor and reports

Get detailed and accurate loading speed reports for your websites and see how your pages are being loaded over time.

Measures the overall time required to load the page in the browser. Page speed is a confirmed Google ranking factor and a strong driver of bounce rate, with slower pages losing a meaningful share of users before they even see the content. Faster pages also tend to convert better, making this a key metric for both SEO and revenue.
JS Execution Time Test
53% of top 100 sites passed
The JavaScript code used by this webpage is executed in less than 2 seconds.
Reports the total time the browser spends parsing, compiling, and executing JavaScript while the page loads. Heavy JavaScript work blocks the main thread and is the primary cause of poor Interaction to Next Paint, the Core Web Vital that replaced First Input Delay in 2024 and that Google uses as part of its ranking algorithms. Reducing bundle size and deferring non-critical scripts directly improves perceived performance.
Page Objects Test
7% of top 100 sites passed
This webpage has less than 20 http requests. A higher number of http requests results in a user's browser needing to request a large number of objects from the server, which will ultimately slow down the loading of your webpage.
Content size by content type
Content type
Percent
Size
javascript
47.3 %
98.41 Kb
font
32.2 %
66.97 Kb
css
13.6 %
28.22 Kb
html
5.2 %
10.82 Kb
image
1.5 %
3.15 Kb
other
0.2 %
450 B
TOTAL
100%
208.00 Kb
Requests by content type
Content type
Percent
Requests
javascript
47.4 %
9
font
26.3 %
5
css
10.5 %
2
html
5.3 %
1
image
5.3 %
1
other
5.3 %
1
TOTAL
100%
19
Content size by domain
Domain
Percent
Size
gamebai1.app
95.1 %
197.76 Kb
static.cloudflareinsights.com
4.9 %
10.23 Kb
TOTAL
100%
208.00 Kb
Requests by domain
Domain
Percent
Requests
gamebai1.app
94.7 %
18
static.cloudflareinsights.com
5.3 %
1
TOTAL
100%
19
Verifies that every resource the page requests, including images, scripts, stylesheets, and fonts, can be successfully retrieved. Broken or unreachable assets can leave the page rendered incorrectly, trigger console errors, and damage both user experience and how search engines perceive page quality.
CDN Usage Test
95% of top 100 sites passed
This webpage is serving all images, javascript and css resources from CDNs.
Detects whether static assets such as images, JavaScript, and CSS are delivered through a Content Delivery Network. CDNs serve files from edge locations close to the user, reducing latency, improving cache hit rates, and offloading traffic from the origin server. The result is faster, more consistent page performance worldwide.
Modern Image Format Test
43% of top 100 sites passed
This webpage is using images in a modern format.
Identifies images served in legacy formats such as JPEG and PNG instead of modern alternatives like WebP or AVIF. Modern formats compress significantly better at equivalent visual quality, which means smaller transfers, faster page loads, and lower data usage for visitors on metered connections.
Image Metadata Test
72% of top 100 sites passed
This webpage is not using images with large metadata.
Flags images carrying disproportionately large embedded metadata such as EXIF data, thumbnails, color profiles, geolocation, and camera information. This metadata is rarely useful on the web and adds bytes to every request without any rendering benefit, making it an easy win for shrinking image payloads.
Image Caching Test
95% of top 100 sites passed
This website is using cache headers for images and the browsers will display these images from the cache.
Inspects whether image responses include caching headers that allow browsers to store them for repeat visits. With proper caching directives, returning visitors retrieve images from the local cache instead of refetching them, producing noticeably faster subsequent page loads.
JavaScript Caching Test
96% of top 100 sites passed
This webpage is using cache headers for all JavaScript resources.
Inspects whether external JavaScript files are served with caching headers that allow browsers to store and reuse them. Cached scripts skip the network on repeat visits, reducing load time and bandwidth for returning users without sacrificing the ability to push fresh code by versioning file URLs.
CSS Caching Test
98% of top 100 sites passed
This webpage is using cache headers for all CSS resources.
Inspects whether external CSS files are served with caching headers that allow browsers to store and reuse them. Cached stylesheets skip the network on repeat visits, reducing load time for returning users while still allowing updates through versioned filenames.
JavaScript Minification Test
98% of top 100 sites passed
All JavaScript files used by this webpage are minified.
Detects whether external JavaScript files are minified by stripping whitespace, comments, and shortening identifiers. Minified scripts are substantially smaller and faster to download and parse, which lowers page load time and improves Core Web Vitals scores.
CSS Minification Test
100% of top 100 sites passed
All CSS resources used by this webpage are minified.
Detects whether external CSS files are minified by removing whitespace, comments, and unused characters. Minification reduces stylesheet size with no functional change, leading to faster downloads and quicker first render.
Render Blocking Resources Test
15% of top 100 sites passed
This webpage is using render blocking resources! Eliminating render-blocking resources can help this webpage to load significantly faster and will improve the website experience for your visitors.

Render Blocking Resources Test

How to pass this test?

This test fails when JavaScript or CSS resources block the browser from rendering visible content. Each render-blocking file delays the first paint, and on slower networks the cumulative impact can be severe. Fixing this issue means inlining the truly critical CSS, deferring or asynchronously loading non-essential scripts, and removing unused code.

Example

<head>
  <!-- Inline only above-the-fold critical CSS -->
  <style>/* critical styles here */</style>

  <!-- Load full stylesheet asynchronously -->
  <link rel="preload" href="/styles/main.css" as="style"
        onload="this.onload=null;this.rel='stylesheet'">

  <!-- Defer non-critical scripts -->
  <script src="/scripts/app.js" defer></script>
</head>

Where to make the change

  • Application code or templates: identify the CSS and JavaScript needed for the initial render and load only those synchronously. Defer the rest.
  • Build pipeline: use a critical CSS extractor (such as critical or penthouse) to generate the above-the-fold styles automatically.
  • WordPress: performance plugins offer "delay JS execution" and "load CSS asynchronously" options that handle most of this without code changes.
  • Headless or framework sites: use the framework's preload and code-splitting hints to control what blocks rendering.

Common causes and how to resolve them

  • Single large stylesheet blocking render: inline critical CSS for the first viewport, load the full stylesheet asynchronously.
  • Synchronous third-party scripts in the head: add defer or async, or move them to the end of the body.
  • Web fonts blocking text rendering: add font-display: swap in @font-face rules so the fallback font shows immediately.
  • Render-blocking @import in CSS: replace with separate <link rel="stylesheet"> tags so the browser can fetch them in parallel.

Best practices

  • Use defer for scripts that need the DOM: they execute after parsing but before DOMContentLoaded.
  • Use async for fully independent scripts: they execute as soon as they download, in any order.
  • Preload the critical request chain: tell the browser early about fonts and key assets with <link rel="preload">.
  • Audit with Lighthouse: the Render-blocking resources audit lists every offending file with the estimated time saved by deferring it.
Identifies JavaScript and CSS resources that the browser must download and process before it can render visible content. Each render-blocking file delays the first paint, and on slower networks the cumulative impact can be severe. Inlining critical styles, deferring non-essential scripts, and removing unused code all help unblock the rendering path.
URL Redirects Test
97% of top 100 sites passed
This URL doesn't have any redirects (which could potentially cause site indexation issues and site loading delays).
Counts the number of HTTP redirects required for the URL to resolve to its final destination. Each hop adds latency and can dilute link equity, while long redirect chains sometimes confuse crawlers and indexing pipelines. Keeping redirects short and direct is a Google recommendation for both performance and SEO.
Time To First Byte Test
99% of top 100 sites passed
The Time To First Byte value of this webpage is 1.016 seconds. To provide a good user experience, Google recommends that sites should strive to have a TTFB of 0.8 seconds or less.
1.016 s
0.8 s
1.8 s

Time To First Byte Test

How to pass this test?

Time to First Byte (TTFB) measures the delay between the browser requesting the page and the first byte of the response arriving. TTFB reflects backend, network, and CDN performance and effectively sets the floor for every other loading metric, since rendering cannot begin until bytes start flowing. Fixing this issue usually means improving server response time, adding edge caching, or reducing redirect chains.

Where to make the change

  • Server and hosting: upgrade to a faster host plan, move to a region closer to your users, and enable HTTP/2 or HTTP/3.
  • CDN: putting the site behind a CDN dramatically reduces TTFB for users far from the origin server. Cache HTML responses at the edge whenever possible.
  • Application code: profile slow endpoints, cache expensive database queries and external API calls, and use streaming or partial responses.

Common causes and how to resolve them

  • Slow server processing: profile the slowest controllers or routes. Database queries, N+1 loops, and synchronous third-party API calls are typical culprits.
  • No edge caching: caching HTML at the CDN reduces TTFB to a single edge round trip. Use rules to bypass cache for logged-in users.
  • Long redirect chains: each hop adds latency before bytes flow. Collapse chains so the URL the user requests resolves to its final destination in one step.
  • Origin in a distant region: a US-only origin makes Asian users wait. Add edge regions or move the origin closer to the audience.
  • HTTP/1.1 or no keep-alive: upgrading to HTTP/2 or HTTP/3 reduces connection setup overhead.

Best practices

  • Target sub-800 millisecond TTFB at the 75th percentile: Google's recommended threshold for a "good" experience.
  • Cache aggressively: the cheapest server work is the work you never do. Static and semi-static pages should be served from cache.
  • Use HTTP/3 where supported: it eliminates head-of-line blocking and reduces handshake latency, especially on mobile networks.
  • Stream the response when possible: sending the head before the rest of the body lets the browser start fetching subresources earlier.
Measures Time to First Byte, the delay between the browser requesting the page and the first byte of the response arriving. TTFB reflects backend, network, and CDN performance and effectively sets the floor for every other loading metric, since rendering cannot begin until bytes start flowing. Sustained high TTFB usually points to slow server processing, missing edge caching, or inefficient redirects.
First Contentful Paint Test
90% of top 100 sites passed
The First Contentful Paint value of this webpage is 1.752 seconds. To provide a good user experience, Google recommends that sites should strive to have a First Contentful Paint value of 1.8 seconds or less.
1.752 s
1.8 s
3 s
Measures First Contentful Paint, the moment when the browser renders the first piece of visible content from the DOM, such as text, an image, or an SVG. FCP is the first signal to the user that the page is actually loading, and faster values are strongly correlated with lower bounce rates and better Core Web Vitals scores.
Largest Contentful Paint Test
77% of top 100 sites passed
The Largest Contentful Paint duration of this webpage is 1.75 seconds. To provide a good user experience, Google recommends that sites should strive to have Largest Contentful Paint of 2.5 seconds or less.
1.75 s
2.5 s
4 s
Largest Contentful Paint element within the viewport:
Text: Cảm ơn vì đã sử dụng WordPress. Đây là bài viết đầu tiên của bạn....
Html: <p class="from_the_blog_excerpt ">
Measures Largest Contentful Paint, the time at which the largest visible element in the viewport, such as a hero image or main heading, finishes rendering. LCP is one of Google's Core Web Vitals and a direct ranking factor, used as a proxy for when the user perceives the page as effectively loaded.
Cumulative Layout Shift Test
91% of top 100 sites passed
The CLS score of this webpage is 0.0000. To provide a good user experience, Google recommends that sites should strive to have a CLS score of 0.1 or less.
0
0.1
0.25
DOM element which contributes the most to CLS score:
Score: 0.0000
Measures Cumulative Layout Shift, the total amount that visible elements move around unexpectedly while the page loads. Layout shifts cause users to misclick and feel the page is unstable, and CLS is one of Google's Core Web Vitals and a direct ranking factor. Common causes include images without explicit dimensions, late-loading fonts, and aggressively injected overlays such as cookie consent banners.

Server and security

Score:95
Failed:1
Warnings:0
Passed:6
URL Canonicalization Test
93% of top 100 sites passed
https://gamebai1.app/ and https://www.gamebai1.app/ resolve to the same URL.
Detects whether different URL variants of the site, such as the apex domain and the www subdomain or HTTP and HTTPS, all resolve consistently to a single canonical version. When the same content is reachable at multiple URLs without proper redirects, search engines may split ranking signals across the variants and become unsure which one to index.
SSL Checker and HTTPS Test
100% of top 100 sites passed
This website is successfully using HTTPS, a secure communication protocol over the Internet.
The certificate is not used before the activation date.
The certificate has not expired.
The hostname "gamebai1.app" is correctly listed in the certificate.
The certificate should be trusted by all major web browsers.
The certificate was not revoked.
The certificate was signed with a secure hash.
Certificate Chain:
Server certificate
Common Name
gamebai1.app
Subject Alternative Names
*.gamebai1.app, gamebai1.app
Not Valid Before
Fri, October 30, 2026 at 3:42:39 AM UTC
Not Valid After
Thu, January 28, 2027 at 3:42:38 AM UTC
Signature Algorithm
ecdsaWithSha384
Issuer
YE2
Intermediate certificate
Common Name
YE2
Organization
Let's Encrypt
Location
US
Not Valid Before
Wed, September 3, 2025 at 12:00:00 AM UTC
Not Valid After
Sat, September 2, 2028 at 11:59:59 PM UTC
Signature Algorithm
ecdsaWithSha384
Issuer
Root YE
Intermediate certificate
Common Name
Root YE
Organization
ISRG
Location
US
Not Valid Before
Wed, May 13, 2026 at 12:00:00 AM UTC
Not Valid After
Thu, September 2, 2032 at 11:59:59 PM UTC
Signature Algorithm
ecdsaWithSha384
Issuer
ISRG Root X2
Root certificate
Common Name
ISRG Root X2
Organization
Internet Security Research Group
Location
US
Not Valid Before
Fri, September 4, 2020 at 12:00:00 AM UTC
Not Valid After
Mon, September 17, 2040 at 4:00:00 PM UTC
Signature Algorithm
ecdsaWithSha384
Issuer
ISRG Root X2
Verifies whether the site is served over HTTPS with a valid TLS certificate. HTTPS encrypts the connection between visitor and server, protecting credentials and other sensitive data in transit, and Google has used it as a positive ranking signal since 2014. Modern browsers also flag non-HTTPS pages as Not Secure, which damages user trust.
Mixed Content Test (HTTP over HTTPS)
100% of top 100 sites passed
This webpage does not use mixed content - both the initial HTML and all other resources are loaded over HTTPS.
Detects whether a page served over HTTPS is loading any sub-resources such as images, scripts, or stylesheets over insecure HTTP. Mixed content weakens the security guarantees of HTTPS, and modern browsers either block the resources outright or warn the user, often breaking the page in the process.
HTTP2 Test
99% of top 100 sites passed
This webpage is using the HTTP/2 protocol.
Verifies whether the page and its resources are delivered over HTTP/2 or newer, rather than the legacy HTTP/1.1 protocol. HTTP/2 introduces multiplexing, header compression, and prioritization, which together reduce latency and allow the browser to load many resources from the same origin far more efficiently.
HSTS Test
84% of top 100 sites passed
This webpage is not using the Strict-Transport-Security header! This is a security header that was created as a way to force the browser to use secure connections when a site is running over HTTPS.

HSTS Test

How to pass this test?

The Strict-Transport-Security (HSTS) response header tells browsers to access the site only over HTTPS, automatically upgrading future requests and refusing to fall back to HTTP. Fixing this issue means configuring the server to send the header on every HTTPS response.

Example

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload

Where to make the change

  • Server configuration: add the header in Nginx (add_header Strict-Transport-Security "max-age=31536000; includeSubDomains" always;), Apache (Header always set Strict-Transport-Security ...), or your application's response middleware.
  • CDN: Cloudflare, Fastly, and CloudFront let you set HSTS at the edge so it applies regardless of origin configuration.
  • Cloud platforms: Netlify and Vercel allow HSTS via headers files (_headers on Netlify, vercel.json on Vercel).

Common causes and how to resolve them

  • Header not sent: add it in the server or CDN config. Confirm in DevTools, Network tab.
  • Header sent only on HTTP responses: HSTS is only honored over HTTPS, so the header must accompany the HTTPS response.
  • Short max-age: a max-age below a few months provides little protection. Bump to a year (31536000) once you are confident HTTPS is stable.
  • includeSubDomains breaking subdomains that lack HTTPS: only add this directive after every subdomain serves HTTPS. Otherwise users will lose access to the HTTP-only ones.

Best practices

  • Start with a short max-age, then ramp up: a one-week max-age lets you back out quickly if something breaks. Increase to a year once stable.
  • Add preload after testing: submit your domain to hstspreload.org so browsers ship with HSTS for your site baked in. Note that removing a preloaded site is slow.
  • Pair with HTTP-to-HTTPS redirects: HSTS only kicks in after a successful HTTPS visit. Until then, redirects do the work.
Checks whether the server sends a Strict-Transport-Security header instructing browsers to only access the site over HTTPS. HSTS protects users from protocol downgrade attacks and accidental exposure to insecure connections, and is a baseline requirement for any site handling sensitive data.
Plaintext Emails Test
97% of top 100 sites passed
This webpage does not include email addresses in plaintext.
Scans the page for email addresses written in plain text. Spambots harvest such addresses to add them to bulk mailing lists, so obfuscating contact emails or replacing them with contact forms helps reduce inbox spam without hiding the address from legitimate visitors.
Unsafe Cross-Origin Links Test
45% of top 100 sites passed
This webpage is not using target="_blank" links without rel="noopener" or rel="noreferrer" attribute.
Inspects external links opened in a new tab to confirm they include the noopener or noreferrer relationship attributes. Modern browsers now apply noopener implicitly to such links, so this is largely a defense for older browsers and a way to keep the destination page from running in the same process as the original tab. Including the attributes explicitly remains a security and performance best practice.

Mobile usability

Score:100
Failed:0
Warnings:0
Passed:3
Meta Viewport Test
92% of top 100 sites passed
This webpage is using a viewport meta tag.
<meta name="viewport" content="width=device-width, initial-scale=1" />
Checks whether the page declares a viewport meta tag that controls how the layout scales on mobile devices. Without it, mobile browsers render the page at a default desktop width and shrink it to fit, producing unreadable text and unusable touch targets. A correct viewport declaration is the foundation of responsive design.
Media Query Responsive Test
98% of top 100 sites passed
This webpage is using CSS media queries, which is the base for responsive design functionalities.
Detects whether the page's stylesheets use CSS media queries to adapt the layout to different screen sizes. Media queries are the primary mechanism for responsive design, allowing typography, spacing, and component arrangement to adjust gracefully from phones to large desktops. Because Google now indexes the web mobile-first, the responsive mobile layout is effectively the version search engines crawl, evaluate, and rank.
Mobile Snapshot Test
Mobile view
A rendered screenshot of how the page appears on a mobile device. Useful for visually confirming that responsive layouts work as intended and for spotting issues such as overflowing content, illegible text, or broken images that automated checks alone may miss.

Advanced SEO

Score:50
Failed:4
Warnings:1
Passed:4
Structured Data Test
66% of top 100 sites passed
This webpage doesn't take the advantages of HTML Microdata or JSON-LD specifications in order to use structured data! View Google's guide for getting started with structured data.

Structured Data Test

How to pass this test?

Structured data is a standardized way to label the entities and relationships on a page so search engines and AI answer engines can understand them. Adding the right schema helps unlock rich result features in SERPs (star ratings, FAQs, product cards, recipes, events) and gives AI answer engines precise facts to extract when generating responses. Fixing this issue means picking the schema types that match your content and embedding them as JSON-LD inside the page <head>. See the Google Search Central structured data guide for the full type catalog.

Example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to choose marathon running shoes",
  "author": { "@type": "Person", "name": "Jane Doe" },
  "datePublished": "2026-04-15",
  "image": "https://example.com/images/hero.jpg"
}
</script>

Where to make the change

  • Raw HTML: embed a JSON-LD block inside the <head>. JSON-LD is Google's preferred format because it does not interleave with visible content.
  • WordPress: a dedicated SEO plugin generates JSON-LD for articles, products, breadcrumbs, and FAQ blocks automatically. Customize the templates for non-standard content.
  • Shopify: Shopify themes emit Product schema by default. Extend with custom types via theme code edits.
  • Wix or Squarespace: built-in blocks for FAQ, recipe, and event content emit schema automatically.
  • Headless or framework sites: generate JSON-LD from your content data in the layout component so every page ships consistent schema.

Common causes and how to resolve them

  • No structured data at all: add at minimum the @type that matches the page (Article for blog posts, Product for product pages, Organization for the homepage).
  • Wrong schema type for the content: using Product schema on an article page misleads search engines. Pick the type that matches what the page actually is.
  • Required properties missing: each schema type has required fields. Validate with the Rich Results Test to surface missing properties.
  • Markup does not match visible content: Google penalizes structured data that asserts facts the page does not show. Reflect what is actually on the page.
  • Multiple conflicting blocks: a theme and an SEO plugin both emit schema for the same entity. Pick one source of truth.

Best practices

  • Validate before shipping: Google's Rich Results Test and Schema Markup Validator catch syntax errors and missing required fields.
  • Use JSON-LD: easier to maintain than Microdata or RDFa and Google's preferred format.
  • Cover the obvious wins: Article, Product, BreadcrumbList, Organization, and FAQPage are the highest-impact types for most sites.
  • Keep schema accurate: wrong or exaggerated schema can lead to Google removing rich result eligibility for the entire site.
Inspects the page for structured data markup such as JSON-LD or Microdata that follows schema.org vocabularies. Structured data helps search engines understand entities and relationships on the page, often unlocking rich result features in SERPs such as star ratings, FAQs, recipes, and product cards. It is also a primary signal AI answer engines use to extract precise facts when generating responses.
Custom 404 Error Page Test
80% of top 100 sites passed
This website is using a custom 404 error page. We recommend to have a custom 404 error page in order to improve the website's user experience by letting users know that only a specific page is missing/broken (and not the entire site), providing them helpful links, the opportunity to report bugs, and potentially track the source of broken links.
Detects whether the site serves a branded, helpful page when a requested URL is not found, instead of the browser's generic error screen. A custom 404 keeps users on the site by offering navigation, search, or suggested links, which reduces frustration and protects engagement metrics that influence both UX perception and indirect SEO outcomes.
Noindex Tag Test
99% of top 100 sites passed
This webpage is using the noindex meta tag! This means that it will be read but not indexed by search engines.

Noindex Tag Test

How to pass this test?

This test fails when the page is being excluded from search engine indexes via a noindex directive in the robots meta tag or X-Robots-Tag HTTP header. A noindex on the wrong page is one of the most common ways important content silently disappears from search results. Fixing this issue means removing the directive from any page that should rank.

Where to make the change

  • Raw HTML: remove <meta name="robots" content="noindex"> from the <head> of pages you want indexed.
  • Server configuration: remove or update X-Robots-Tag: noindex response headers for affected URL paths.
  • WordPress: in the post or page editor, your SEO plugin has a "Search engine visibility" toggle. Make sure it is set to allow indexing. Also check Settings, Reading, "Discourage search engines" — this site-wide flag must be off.
  • Shopify: certain templates and resource types (search results, cart) are noindexed by default and should stay that way. For other URLs, edit theme.liquid to remove the conditional noindex.
  • Headless or framework sites: remove the meta tag from the page's metadata configuration or layout file.

Common causes and how to resolve them

  • Site-wide noindex left over from staging: the most common cause. Disable the global setting after launch.
  • Per-page noindex set in the CMS by mistake: review the page's SEO settings and toggle indexing back on.
  • X-Robots-Tag header set by server config: check the server or CDN rules; remove the header for production URLs.
  • Noindex on category or tag pages that should rank: some SEO plugins noindex archives by default. Override the setting for archives that earn organic traffic.

Best practices

  • Verify with URL Inspection in Search Console: the live test confirms whether Google currently sees the page as indexable.
  • Audit after migrations: staging sites are usually noindexed; verify the directive is removed before traffic resumes.
  • Keep noindex for thin or duplicate pages: not every page should rank. Internal search results, paginated archives, and login pages benefit from noindex.
Detects whether the page is being excluded from search engine indexes via a noindex directive in the robots meta tag or X-Robots-Tag HTTP header. A noindex on the wrong page is one of the most common ways important content silently disappears from search results, so verifying its absence on pages meant to rank is critical.
Canonical Tag Test
93% of top 100 sites passed
This webpage does not use the canonical link tag.
Detects whether the page declares a canonical link tag indicating its preferred URL. Canonical tags consolidate ranking signals across duplicate or near-duplicate URLs onto a single authoritative version, which prevents search engines from splitting authority across variants caused by query parameters, session IDs, or alternate paths. They also help AI crawlers identify the source of truth when citing the page.
Nofollow Tag Test
This webpage is using the nofollow meta tag! We recommend to use this tag carefully since search engines will not crawl all links from this webpage.

Nofollow Tag Test

How to pass this test?

This test reports on whether the page applies a nofollow directive that tells search engines not to follow outbound links. The nofollow attribute (and the related sponsored and ugc values) controls how link equity flows from your page. Fixing this issue means using the right rel value on each external link based on its purpose so signals are passed only where you intend.

Where to make the change

  • Raw HTML: add rel="nofollow", rel="sponsored", or rel="ugc" to specific outbound links rather than blanket-applying them site-wide.
  • WordPress: the block editor offers a "mark as nofollow" option per link, and SEO plugins can auto-tag external links by domain.
  • Shopify, Wix, Squarespace: editor-generated links allow rel attribute toggles; manual HTML embeds need them set explicitly.
  • Headless or framework sites: wrap external links in a component that decides the rel based on the link's classification.

Common causes and how to resolve them

  • Site-wide nofollow on every external link: overly aggressive. Reserve nofollow for sponsored, untrusted, or user-generated content.
  • Sponsored content not labeled: use rel="sponsored" on paid placements and affiliate links to comply with Google's link spam policy.
  • User-generated content unmarked: comments, forum posts, and review user submissions should use rel="ugc".
  • Trusted editorial links nofollowed: these should pass equity. Remove the nofollow.

Best practices

  • Use the most specific value: sponsored for paid links, ugc for user content, nofollow for everything else you want to disclaim. They can be combined: rel="sponsored noopener".
  • Do not nofollow internal links: "PageRank sculpting" with internal nofollow no longer works and just wastes crawl signal.
  • Audit periodically: as content ages, sponsored relationships change. Review affiliate and partner links once a year.
Detects whether the page applies a nofollow directive, either through a robots meta tag, an X-Robots-Tag header, or per-link rel attributes, that tells search engines not to follow outbound links. Google recommends nofollow for sponsored links and for user-generated content where the linked sites are not vetted, so its presence or absence has real consequences for how link equity flows.
Disallow Directive Test
Your robots.txt file includes a disallow command which instructs search engines to avoid certain parts of your website! You are advised to confirm if access to these resources or pages are intended to be blocked (e.g., if they contain internal-only content or sensitive information).
Surfaces the disallow rules declared in the site's robots.txt file. Disallow directives tell search engine crawlers not to access specific files, paths, or directories, which is useful for keeping admin sections and duplicate content out of indexes but dangerous when applied too broadly, since over-blocking can hide important pages from search.
Meta Refresh Test
98% of top 100 sites passed
This webpage is not using a meta refresh tag.
Detects whether the page uses a meta refresh tag to automatically reload or redirect after a delay. Meta refresh is largely obsolete, hurts accessibility by jumping focus and disorienting screen reader users, and is a weaker signal to search engines than a proper server-side 301 redirect. Its presence usually indicates outdated implementation worth updating.
SPF Records Test
94% of top 100 sites passed
This DNS server is not using an SPF record! SPF (Sender Policy Framework) allows administrators to specify which hosts are allowed to send mail from a given domain by creating a specific SPF record or TXT record in the Domain Name System (DNS). You can find more information about SPF records here.

SPF Records Test

How to pass this test?

The Sender Policy Framework (SPF) DNS record lists the mail servers authorized to send email on behalf of your domain. Receiving servers use it to verify that messages claiming to come from your domain are legitimate, which significantly reduces the chance of email being marked as spam. Fixing this issue means publishing an SPF record in your DNS that includes every legitimate sender and ends with a strict policy.

Example

example.com.  TXT  "v=spf1 include:_spf.google.com include:mailgun.org ~all"

Where to make the change

  • DNS provider: add a TXT record at the domain root with the SPF policy. Cloudflare, Route 53, Namecheap, GoDaddy, and similar all expose a TXT record editor.
  • Email providers: Google Workspace, Microsoft 365, and most transactional email services publish their required SPF include directives in their setup documentation.

Common causes and how to resolve them

  • No SPF record at all: add one. Even a minimal record (v=spf1 include:_spf.google.com ~all) is better than nothing.
  • Multiple SPF records: SPF only allows one TXT record per domain. Merge multiple records into a single one with all required include: directives.
  • Policy too permissive: ending with +all authorizes anyone to send as your domain. Use ~all (soft fail) or -all (hard fail) instead.
  • Missing legitimate senders: add an include: for every transactional email service (SendGrid, Mailgun, Postmark) and every marketing platform you use.
  • Too many DNS lookups: SPF caps include lookups at ten. Flatten or consolidate include: chains if you exceed it.

Best practices

  • Pair SPF with DKIM and DMARC: SPF alone is not enough. DKIM signs messages cryptographically; DMARC tells receivers what to do when SPF or DKIM fails.
  • Start with ~all, move to -all: soft fail lets you observe before strict enforcement. Move to hard fail once you are confident no legitimate sender is missing.
  • Test deliverability: tools such as MXToolbox SPF check or Google Postmaster Tools surface SPF problems before users complain.
  • Audit annually: as you add or remove email vendors, the SPF record needs to keep up.
Checks the domain's DNS for a Sender Policy Framework record. SPF lets receiving mail servers verify that messages claiming to come from the domain were actually sent by an authorized mail server, which significantly reduces the chance of legitimate email being marked as spam and protects the domain's sender reputation.
Ads.txt Validation Test
67% of top 100 sites passed
This website doesn't use an ads.txt file! Ads.txt is a text file that contains a list of Authorized Digital Sellers. The purpose of ads.txt files is to give advertisers and advertising networks the ability to verify who is allowed to sell advertising on your website.
Validates the format of the site's ads.txt file, which publishers use to declare which advertising vendors are authorized to sell their inventory programmatically. A correctly formatted ads.txt protects against domain spoofing in the ad supply chain and is required for inclusion in many premium advertising marketplaces.

Dominate search today on Google and AI Engines.

Join 85,000+ SaaS Marketers, Growth Agencies, Content-Led Companies and E-commerce Brands.

See Pricing
Dashboard preview showing SEO site checkup metrics, page group insights, and issue prioritization