A new or recently changed website
Confirm that the public homepage exposes basic crawl, canonical, mobile, metadata, and indexability signals after a launch or redesign.
Run a free public-homepage overview for response, security, crawl files, metadata, headings, links, images, structured data, and indexability signals.
Add your email, domain, market, and an optional competitor. Your detailed report opens on a separate page.
The free TeamSoda domain overview requests one public homepage and reports observable facts about the response, HTTPS, crawl files, indexability, metadata, headings, links, images, social metadata, and structured data. It is a transparent first-pass diagnostic—not an estimate of traffic, rankings, backlinks, leads, or revenue.
The tool requests one publicly accessible homepage and reports facts visible in the returned HTML and standard crawl files.
Foundational gaps can make a site harder to crawl, interpret, preview, or maintain. A missing title, accidental noindex, broken canonical, absent mobile viewport, unclear H1, or incomplete image alternatives deserves attention because each affects a different part of accessibility and search readiness.
A strong homepage score does not prove that the site ranks, attracts qualified traffic, earns links, appears in AI answers, or converts visitors. It also does not inspect every template, service page, product page, location page, script, redirect, or analytics implementation.
Start with failed fundamentals, review warnings in the context of the page's purpose, and avoid changing a valid implementation just to chase a perfect score. When the decision affects architecture, migration, content investment, or market strategy, validate it with a broader crawl and human review.
Use the tool for a quick orientation before deciding whether a technical problem needs closer investigation.
Confirm that the public homepage exposes basic crawl, canonical, mobile, metadata, and indexability signals after a launch or redesign.
Check for obvious public-page problems before assuming a ranking change came from content, competition, links, or an algorithm update.
Create a shared factual snapshot that helps the team ask a more precise question about the site.
Each result is based on the fetched public homepage and standard crawl-file locations available at the time of the request.
Requested and final URL, response status, redirect destination, HTTPS, and a directional response-time snapshot.
Robots directives, public robots.txt, the standard sitemap path, canonical URL, language, and mobile viewport.
Title, meta description, primary heading count, visible page depth, links, and social-preview metadata.
Image alternative coverage and the presence of JSON-LD that may help describe entities or page purpose.
The sequence is visible from the beginning. Research, recommendations, implementation, and measurement stay connected to the business question that started the work.
Submit only a public HTTP or HTTPS website. Private hosts, direct IP addresses, authenticated pages, and local development addresses are rejected.
The checker follows the allowed request path, records the final public response, and tests standard robots and sitemap locations.
Read the observed detail and explanation behind each pass, warning, or issue instead of treating the total as the diagnosis.
Use a broader technical audit when the concern involves templates, JavaScript, redirects, faceted navigation, migrations, internal links, or site-wide indexation.
No single metric tells the whole story. TeamSoda combines leading search signals with customer and commercial outcomes wherever reliable data is available.
How many directly observable homepage fundamentals are present and internally coherent.
Which failed signals can materially affect access, interpretation, social previews, accessibility, or maintenance.
Whether the evidence points toward a precise fix, a full-site crawl, or a business and content review.
No. It checks one public homepage plus standard robots.txt and sitemap.xml locations. A full technical audit needs a broader crawl and often platform-specific evidence.
Those values require approved analytics, search-platform data, or licensed third-party datasets. TeamSoda does not infer them from a domain name.
No. The score summarizes inspected fundamentals. Rankings also depend on relevance, competition, content usefulness, authority, demand, history, and many other factors.
No. A sitemap can use another location and may be declared in robots.txt. The result is a prompt to verify the configuration, not an automatic diagnosis.
Add a little business context so the automated findings can be translated into a focused search and AI visibility plan.
Sample up to eight same-domain pages and review metadata, headings, indexability, schema, image alternatives, content depth, crawl foundations, and repeated signals.
Read moreUse TeamSoda's SEO crawl, website performance checker, domain overview, and SEO Plan tool to understand the starting point and organize the next actions.
Read moreRequest a practical first look at your technical foundation, content coverage, search intent, AI visibility, and conversion path.
Read moreResolve the crawl, indexation, performance, structure, and schema issues that keep search systems from understanding your site.
Read more