SEOWebsiteTool
86Grade B

commlinq.com

Leading Washington VoIP Provider | Commlinq

1 failed · 7 warnings · 21 passed

Audited Sun, 12 Jul 2026 06:30:50 GMT · https://commlinq.com/

Meta & Head

22.9/25

Title, description, canonical, social tags — what search engines read first.

  • Canonical URLmedium impactlow effort

    No <link rel="canonical"> found

    When the same page is reachable at several URLs — tracking parameters, trailing-slash variants, http vs https — search engines may split ranking signals across the duplicates. A canonical tag names the one version that should get all the credit. Add <link rel="canonical" href="https://www.example.com/page/"> to the <head>, pointing at the page's preferred absolute URL. Double-check it's self-referencing on the primary version: a canonical that points at the wrong page can quietly de-index the right one.

  • Faviconlow impactlow effort

    No <link rel="icon"> and /favicon.ico does not respond

    Google displays favicons beside mobile search results, and browsers show them in tabs, bookmarks, and history — a missing icon makes your listing look generic and less trustworthy next to competitors. Create an icon of at least 48x48 pixels, serve it at /favicon.ico, and reference it with <link rel="icon" href="/favicon.png" type="image/png"> in <head>. Make sure robots.txt doesn't block the icon's path — search engines must be able to crawl it to display it.

7 passing checks
  • Title tag<title> is "Leading Washington VoIP Provider | Commlinq" (43 characters)
  • Meta descriptionMeta description is "Commlinq offers best of class VOIP solutions for businesses in the Seattle metro area, Bellingham, and Eastern Washington." (122 characters)
  • Viewport meta tagViewport is "width=device-width, initial-scale=1"
  • Character encoding declaredCharacter encoding is declared
  • Open Graph tagsAll core Open Graph tags present (og:title, og:description, og:image, og:url)
  • Twitter card tagtwitter:card is "summary"
  • Page allows indexingNo restrictive robots meta tag

Content & Structure

19.5/25

Headings, copy depth, images, structured data, internal linking.

  • Image alt textmedium impactlow effort

    2 of 5 images have alt text

    Alt text is how search engines understand what an image shows — it feeds image-search rankings and is what screen readers announce to blind visitors. Add a short, specific alt attribute to every meaningful image, describing the content rather than listing keywords: alt="Golden retriever puppy playing in snow" beats alt="dog puppy pet animal". Give purely decorative images an empty alt="" instead of omitting the attribute, so assistive technology knows to skip them rather than reading out the filename.

  • Structured data (JSON-LD)medium impactmedium effort

    No JSON-LD structured data blocks found

    Structured data makes your listing eligible for rich results — star ratings, FAQs, breadcrumbs, product prices — which occupy more space on the results page and draw more clicks than plain blue links. Add a <script type="application/ld+json"> block with a schema.org type that matches the page: Organization or WebSite for a homepage, Article for posts, Product for product pages. Only mark up content actually visible on the page — markup for invisible content violates Google's guidelines and can earn a manual action.

  • Heading hierarchylow impactlow effort

    Heading level jumps from h2 ("Get Connected with commlinq Technologies") to h4 ("On Premise Solutions")

    Headings form the page's outline; when levels jump (h2 straight to h4), search engines and screen readers get a broken table of contents and the relationship between sections turns ambiguous. Fix the jump by stepping down one level at a time — promote the deeper heading, or add the missing intermediate level. The usual cause is choosing heading tags for their default font size; set sizes in CSS instead and let the tags reflect actual document structure.

5 passing checks
  • Single H1 heading1 h1 found: "VOIP video Mobility Collaboration Business TExting Virtual Fax"
  • Word count3041 words of visible text
  • HTML lang attribute<html lang="en-US">
  • JavaScript-dependent contentvisible text ~1139 chars in the initial HTML
  • Internal linking23 internal, 1 external links

Technical

22.2/25

HTTPS, redirects, robots, sitemap, speed, crawlability.

  • Short redirect chainmedium impactlow effort

    https://commlinq.ai/ (301) → https://commlinq.com/

    Every redirect hop adds a round-trip before the visitor sees anything, each hop can leak a little link equity, and crawlers abandon long chains — which can leave the destination page undiscovered. Trace the chain above and point the first URL directly at the final destination in a single 301; commonly this means merging separate http-to-https and non-www-to-www rules into one combined redirect. Also update internal links to reference the final URL directly, so most visitors never enter the chain at all.

  • XML sitemap availablemedium impactlow effort

    sitemap.xml is valid but robots.txt does not reference it

    Your sitemap is valid, but robots.txt never mentions it, so crawlers you haven't manually notified may never find it — the robots.txt reference is the universal discovery mechanism. Add one line to robots.txt: "Sitemap: https://www.example.com/sitemap.xml", using the full absolute URL (a relative path is invalid here). The line can go anywhere in the file, and you can list several sitemaps. Also submit it in Google Search Console to get indexing-coverage reporting on top of discovery.

  • Response compression enabledlow impactlow effort

    no content-encoding header

    This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.

9 passing checks
  • Served over HTTPSfinal URL uses https://
  • HTTP redirects to HTTPShttp:// redirects to https://
  • No mixed content0 http:// subresource references
  • robots.txt present and permissiverobots.txt exists and allows crawling
  • Fast time to first byte193 ms
  • Reasonable HTML size99.4 KB
  • Missing pages return 404missing paths return HTTP 404/410
  • www and non-www resolve consistentlywww and non-www converge on the same host
  • HTML5 doctype<!DOCTYPE html> present

Performance

Core Web Vitals scoring via Google PageSpeed is coming soon.

Share your score

Embed this live badge on your site — it updates whenever the audit is re-run.

SEO score badge for commlinq.com

More “c” sitesRecent audits

commlinq.com — SEO Score 86/100 (Grade B) | SEO Website Tool