SEO report for ignitetech.ai

Real-world speed Google PageSpeed

Loading Core Web Vitals from Google… this can take up to 30 seconds.

Authority & backlinks

Looking up which websites link to ignitetech.ai…

Indexing & crawling 100%

Can search engines reach, read and index this page?

• ✓

  Status codecritical

  The page returned HTTP 200.

• ✓

  Indexablecritical

  No noindex instruction – the page can appear in search.

• ✓

  robots.txthigh

  robots.txt found.

  Googlebot is allowed to crawl this page.

• ✓

  XML sitemaphigh

  Sitemap index found at https://ignitetech.ai/sitemap_index.xml listing 11 sitemaps.

  Declared in robots.txt.

  Most recent lastmod: 2026-10-15T12:55:44+00:00.

• ✓

  Canonical URLhigh

  Canonical: https://ignitetech.ai/software-library/fogbugz/

  Points to this page (self-referencing).

• ✓

  Redirectshigh

  1 redirect before the page loaded.

  https://fogbugz.com/ → https://ignitetech.ai/software-library/fogbugz/

  A single redirect to your preferred address is normal; just make sure your own links use the final address.

• ✓

  www / non-wwwmedium

  www.ignitetech.ai redirects to ignitetech.ai.

Search snippet & sharing 58%

How the page looks in Google results and when shared.

• ✗

  Title tagcritical

  No <title> found.

  Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.

  Preview and measure your title with the free title tag checker

  Read the guide: how to write title tags

• ✓

  Meta descriptionhigh

  150 characters, ~940px of ~990px.

  Good length.

  Google sometimes rewrites descriptions to match the search; a good one is still used most often.

• ✓

  Open Graph & social cardsmedium

  Open Graph title and image set.

  Twitter/X card: summary_large_image.

• ✓

  Faviconlow

  Favicon linked (Google shows it next to results).

• ✓

  Languagelow

  lang="en-US"

Content quality 42%

Is there enough clear, useful text that matches what the page targets?

• ✓

  Word countmedium

  463 words of main content (menus and footer excluded).

  Google has no minimum word count – this is a rough guide to whether the page answers the question in full.

• ✓

  Readabilitymedium

  Flesch reading ease 52 (fairly easy), about 14 words per sentence.

• i

  Topic focushigh

  No title keywords to compare.

• ✗

  H1 headingcritical

  No H1 heading.

  Fix: Use one H1 that states the page topic with its main keyword.

• !

  Heading structuremedium

  10 headings for 463 words.

  2 skipped level(s), e.g. H2 → H4.

  1 empty heading(s).

  Fix: Use H2s for main sections and H3s inside them, without skipping levels.

  Read the guide: the on-page SEO checklist

• ✗

  Text-to-code ratiolow

  3% of the HTML is visible text.

  Fix: Trim unused markup, inline scripts and builder bloat.

AI search readiness 81%

Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?

• ✓

  AI crawler accesshigh

  Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.

• ✓

  Snippet controlshigh

  No snippet restrictions – search and AI answers can quote this page.

• ✓

  llms.txtlow

  /llms.txt found.

• ✗

  Question-led contentmedium

  No headings phrased as questions.

  Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.

  Read the guide: how to write SEO content

• ✓

  Entity clarityhigh

  Identified as: Organization.

  2 official profile link(s) (sameAs).

• ✓

  Freshness signalsmedium

  The page shows when it was published or last updated.

• !

  Trust pages (E-E-A-T)medium

  Links found to about and privacy; missing contact.

  Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.

Structured data 100%

Machine-readable facts for rich results and AI.

• ✓

  JSON-LD present & validhigh

  1 JSON-LD block(s): WebPage, ReadAction, ImageObject, BreadcrumbList, ListItem, WebSite, SearchAction, EntryPoint, PropertyValueSpecification, Organization.

  All blocks parse correctly.

• ✓

  Required propertiesmedium

  Key types include Google's required properties.

• ✓

  Breadcrumbslow

  BreadcrumbList markup present.

Links 75%

Internal linking, anchor text and broken links.

• ✓

  Internal linkinghigh

  26 internal and 6 external links.

• ✗

  Anchor text qualitymedium

  No link text points to two different pages.

  6 link(s) with no text at all.

  Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.

  Check every link's wording with the free anchor text checker

  Read the guide: internal linking

• ✓

  Broken links (sample)high

  Checked 11 internal link(s).

  No broken links found.

Performance 56%

Speed signals from the HTML and server. Real-user Core Web Vitals load below.

• ✓

  Server response (TTFB)high

  146 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).

• ✓

  HTML sizemedium

  108 kB of HTML.

• ✓

  Compressionmedium

  Compressed with br.

• ✗

  Render-blocking resourceshigh

  3 blocking script(s) and 22 stylesheet(s) in <head>.

  Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.

  Read the guide: Core Web Vitals

• ✗

  Scripts & third partiesmedium

  54 script tag(s); files loaded from 6 other domain(s): cdnjs.cloudflare.com, cdn.jsdelivr.net, code.jquery.com, js.hs-scripts.com, googletagmanager.com, unpkg.com.

  Fix: Remove unused tracking and widget scripts; every third party adds connection time.

  Read the guide: Core Web Vitals

• ✗

  Imagesmedium

  18 image(s).

  9 without width/height – can cause layout shift (CLS).

  9 image(s) after the first three aren't lazy-loaded.

  3 use WebP/AVIF or responsive srcset.

  Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.

  Read the guide: image SEO

• ✓

  Cachinglow

  Cache-Control: max-age=600, must-revalidate

• ✓

  HTTP/3low

  Server advertises HTTP/3 (faster on mobile networks).

Security 58%

Visitor safety signals that browsers and Google check.

• ✓

  HTTPScritical

  Secure HTTPS with no mixed content.

• ✗

  HTTP → HTTPS redirecthigh

  http:// does not redirect to https://.

  Fix: 301-redirect all http:// requests to https://.

  Read the guide: fixing a "Not secure" warning

• !

  HSTSmedium

  HSTS: max-age=86400

  max-age is under 6 months – browsers will forget it quickly.

  Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.

  Read the guide: the technical SEO checklist

• ✓

  Security headerslow

  Present: nosniff, Referrer-Policy, Permissions-Policy, clickjacking protection.

• ✗

  Server fingerprintlow

  X-Powered-By reveals “WP Engine”.

  Fix: Remove X-Powered-By so attackers can't see your software versions.

Mobile & accessibility 38%

Usable on phones and by everyone – Google indexes the mobile version.

• !

  Mobile viewportcritical

  viewport: width=device-width, initial-scale=1, maximum-scale=1 – blocks pinch-zoom

  Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.

  Read the guide: mobile-friendly websites

• ✗

  Image alt textmedium

  5 of 18 images have no alt attribute.

  Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).

  Read the guide: image SEO

• ✓

  Form labelsmedium

  All 4 form fields are labelled.

• ✗

  Link nameslow

  6 link(s) have no readable name for screen readers.

  Fix: Add text or aria-label to icon-only links.

  Read the guide: internal linking

• ✗

  Tap-to-contactmedium

  No tel: or mailto: links.

  Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.

  Read the guide: mobile-friendly websites

Local SEO not scored

This site doesn't look like a local business, so these checks are shown for information and not scored.

• i

  LocalBusiness markuphigh

  No LocalBusiness structured data.

• i

  Contact details on pagemedium

  No phone number found.

  No postcode found (fine for service-area businesses).

• i

  Map & directionslow

  No map or directions link.