SEOWebsiteTool
73Grade C

webliftersolutions.com

Weblifter | Agencia de Software a Medida y Automatización con IA

2 failed · 11 warnings · 16 passed

Audited Sun, 26 Jul 2026 04:45:51 GMT · https://webliftersolutions.com/

Meta & Head

18.1/25

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

  • Open Graph tagsmedium impactlow effort

    No Open Graph tags found

    Open Graph tags control how your page looks when shared on Facebook, LinkedIn, Slack, WhatsApp, and most chat apps; without them, links render as a bare URL or with guessed text, and far fewer people click through. Add four meta tags to <head>: og:title, og:description, og:url, and og:image — an image around 1200x630 pixels works well across platforms. Use absolute https:// URLs for og:image and og:url; relative paths are the most common reason preview images silently fail to appear.

  • Title taghigh impactlow effort

    <title> is "Weblifter | Agencia de Software a Medida y Automatización con IA" (64 characters)

    Search engines truncate titles past roughly 60 characters and often rewrite very short or vague ones, so the message you wrote may never actually be shown. Rewrite the title to 30–60 characters that lead with the primary keyword and end with your brand, e.g. "Merge PDF Files Online Free | YourBrand". Front-load the important words, since truncation always cuts from the end. Don't pad a short title with repeated keywords just to hit the range — clarity wins clicks, not length.

  • 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.

  • Twitter card taglow impactlow effort

    No twitter:card meta tag found

    X (Twitter) layers its own card markup on top of Open Graph, and without a twitter:card tag your shared links may render as plain text instead of a large image preview. Add <meta name="twitter:card" content="summary_large_image"> alongside your Open Graph tags; X will fill in the title, description, and picture from og:title, og:description, and og:image. Keep og:image an absolute URL — a relative or missing image is the usual reason cards show up without a picture.

5 passing checks
  • Meta descriptionMeta description is "Sistemas a medida, automatizaciones con IA y automatización de procesos que quitan el trabajo manual de tus operaciones." (120 characters)
  • Viewport meta tagViewport is "width=device-width, initial-scale=1"
  • Character encoding declaredCharacter encoding is declared
  • FaviconA <link rel="icon"> is present
  • Page allows indexingNo restrictive robots meta tag

Content & Structure

17.2/25

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

  • Single H1 headinghigh impactlow effort

    2 h1 headings found: "Más Valor.", "Menos Trabajo."

    Multiple h1s split the page's main-topic signal, leaving search engines to guess which headline actually defines the page. Keep the one h1 that best states the primary topic and demote the rest to h2 or h3, so the outline reads as a single subject with subtopics. A frequent culprit is a site logo or blog title wrapped in an h1 inside the shared header template — change that to a <div> or <p> and reserve h1 for the page's own content.

  • Word counthigh impactlow effort

    516 words of visible text

    With only a few hundred words, this page gives search engines little to index and often loses to more thorough competitors targeting the same query. Expand it toward 600+ words of genuinely useful material: answer the questions visitors arrive with, and add examples, specifics, an FAQ section, or step-by-step detail. Don't pad with fluff or repeat keywords to hit a number — length should be a byproduct of covering the topic properly, never the goal itself.

  • Image alt textmedium impactlow effort

    16 of 28 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.

4 passing checks
  • Heading hierarchy18 headings in order without skipped levels
  • HTML lang attribute<html lang="es">
  • JavaScript-dependent contentvisible text ~3580 chars in the initial HTML
  • Internal linking23 internal, 0 external links

Technical

19.3/25

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

  • www and non-www resolve consistentlyhigh impactlow effort

    www and non-www resolve to different final hosts

    The www and non-www versions of your domain resolve to different hosts, so search engines treat them as two separate sites and split links, rankings, and crawl attention across duplicate copies. Pick one canonical host — either works; consistency is what matters — and 301-redirect the other to it at the CDN or server level, e.g. a Cloudflare redirect rule or an .htaccess RewriteRule sending example.com to www.example.com. Then use the chosen host everywhere: internal links, canonical tags, and the sitemap.

  • robots.txt present and permissivemedium impactlow effort

    no robots.txt found

    Without a robots.txt, crawlers assume everything is allowed — not fatal, but you lose the ability to keep them out of low-value areas (internal search results, carts, admin paths) and the standard place to advertise your sitemap. Create a plain-text robots.txt at the site root with at least a "User-agent: *" line and "Sitemap: https://www.example.com/sitemap.xml". Don't use it to hide sensitive URLs, though — the file is public, and disallowing a page doesn't remove it from the index; use noindex or authentication for that.

  • XML sitemap availablemedium impactlow effort

    no sitemap.xml found

    Without an XML sitemap, search engines discover pages only by following links, so new, deep, or weakly linked pages get found slowly or not at all. Generate one at /sitemap.xml — most frameworks and CMSs have a generator built in or as a plugin — listing every canonical, indexable URL, then add "Sitemap: https://www.example.com/sitemap.xml" to robots.txt and submit it in Google Search Console. Keep it clean: listing redirected, noindexed, or 404 URLs erodes crawler trust in the whole file.

  • 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.

  • Missing pages return 404low impactlow effort

    missing paths return a non-404 status (soft 404)

    URLs that don't exist on your site return a success status instead of 404 — search engines call these soft 404s, keep recrawling them, and may index the useless placeholder pages, wasting crawl budget that should go to real content. Configure your server or framework to return an actual 404 status (or 410 for permanently removed content) along with your error page. The classic mistake is serving a friendly "page not found" template with a 200 status — crawlers ignore the visible message; only the status code counts.

7 passing checks
  • Served over HTTPSfinal URL uses https://
  • HTTP redirects to HTTPShttp:// redirects to https://
  • No mixed content0 http:// subresource references
  • Short redirect chainno redirects; URL resolves directly
  • Fast time to first byte406 ms
  • Reasonable HTML size65.9 KB
  • 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 webliftersolutions.com

More “w” sitesRecent audits