NOTABIS SEO / LEARN
Practical guides for the SEO findings NOTABIS measures. Learn what an issue means, how to verify it, when it is intentional, and how to fix it safely.
Technical SEO · 9 Sep 2026
A viewport declaration tells mobile browsers how to size and scale a page. Its presence is a baseline mobile-rendering check, not proof that a page is responsive or usable.
Read guide →Technical SEO · 9 Sep 2026
Redirects are often correct, but links should usually point directly to the final URL. NOTABIS reports when a crawled requested URL resolves somewhere else so you can review intent, chains, and internal links.
Read guide →Crawlability · 9 Sep 2026
A sitemap-unavailable finding means a declared sitemap could not be fetched or processed during the audit. Check the exact URL, response, content type, XML, redirects, and access controls before changing your site.
Read guide →Crawlability · 9 Sep 2026
A noindex directive asks compliant search crawlers not to include a page in search results. It is correct for many private or utility pages, but harmful when placed on a public page that should be discoverable.
Read guide →Performance · 9 Sep 2026
Large HTML can increase transfer and parsing work, but size alone does not prove a page is slow. NOTABIS flags responses over 500,000 bytes so you can inspect the content and delivery path.
Read guide →Performance · 9 Sep 2026
A slow response finding means the measured request took more than two seconds in that audit. Investigate server work, database calls, caching, network path, and load before choosing a fix.
Read guide →Performance · 9 Sep 2026
HTTP compression reduces transfer size for compressible responses. NOTABIS flags HTML responses that did not advertise Content-Encoding, but the finding is a review signal rather than a complete performance diagnosis.
Read guide →Images · 9 Sep 2026
Give informative images useful alternative text and mark decorative images with an empty alt attribute. Missing alt text is primarily an accessibility problem; the correct wording depends on the image’s purpose.
Read guide →Content · 9 Sep 2026
Multiple H1 elements are not automatically an SEO failure, but they can indicate unclear document structure or an accidental template duplicate. Review the visible hierarchy and page purpose before changing them.
Read guide →Metadata · 9 Sep 2026
Title length is a review signal, not a magic ranking threshold. Write a concise title that identifies the page, puts important context early, and remains accurate when truncated.
Read guide →Images · 9 Sep 2026
Declare intrinsic image dimensions or an equivalent aspect ratio so browsers can reserve space before images load. The fix should preserve the image’s intended crop and responsive behaviour.
Read guide →Links · 9 Sep 2026
A sitemap-only page was found in the sitemap but no crawled internal HTML page linked to it. That is a discoverability review, not proof that the URL is broken or worthless.
Read guide →Site health · 9 Sep 2026
Security headers deserve a security review, but their absence in an SEO crawl is not a complete vulnerability assessment. Configure them with the application’s actual resource, embedding, and privacy requirements.
Read guide →Metadata · 9 Sep 2026
Social metadata helps sharing systems understand a page preview. Missing fields are an interoperability review and do not prove that every social platform will display a broken card.
Read guide →Performance · 9 Sep 2026
A render-blocking finding identifies markup patterns that may delay first rendering. It is a candidate list, not measured proof of user-visible impact; validate changes with performance evidence.
Read guide →Run a NOTABIS SEO audit to crawl your pages and connect measured findings with practical guidance.
Run an audit →