webworks.ie: homepage SEO audit

The website is doing really well overall, but the biggest thing to fix right now is adding a description to your homepage — this is the snippet that shows up in Google search results, and without it, people won't know what your site is about before clicking. The good news is that your site works beautifully on mobile phones and is secure, which is excellent. Here's what I'd recommend doing first: spend 15 minutes writing a clear, friendly description (about 150 characters) that explains what WebWorks does, then add it to your homepage. Once that's done, you'll have knocked out the main issue holding you back!

1. 01
   CriticalMeta Tags

   This page is missing a description

   The meta description is the summary under your link in Google. Without it, Google writes its own — usually a random sentence from your page that rarely makes people want to click.

   How to fix: Add a <meta name="description"> tag with 1–2 sentences describing what your business offers and why to choose you (70–160 characters).

2. 02
   ImportantPerformance

   5 scripts are delaying this page

   Scripts in the page header without 'async' or 'defer' force the browser to wait before showing anything. Adding one of those keywords lets the content appear sooner.

   How to fix: Add the defer (or async) attribute to <script> tags in your <head>, or move them to the end of the <body>.

3. 03
   ImportantContent & SEO Readiness

   6 of 9 images have no description

   Alt text describes an image to Google and to visually impaired visitors. It also helps you show up in Google Image search. Add a short, plain description to each image.

   How to fix: Add an alt attribute to each image describing what it shows, e.g. alt="blue ceramic mug on a wooden table".

4. 04
   MinorHeadings

   Headings skip levels

   Headings work like a table of contents (H1 → H2 → H3). This page jumps a level somewhere, which makes the structure harder for Google and screen readers to follow.

   How to fix: Use headings in order — don't jump from H2 straight to H4. Pick heading levels for structure, not for font size (use CSS for styling).

5. 05
   MinorContent & SEO Readiness

   No robots.txt file found

   A robots.txt file tells search engines which pages they may visit. It's a small file at the root of the site — having a valid one is a basic sign of a well-maintained website.

   How to fix: Create a /robots.txt file (even a simple one allowing all crawlers and linking the sitemap) at the root of the domain.

6. 06
   MinorContent & SEO Readiness

   No sitemap found

   A sitemap is a list of your pages that helps Google discover and index them faster. Most website builders and SEO plugins create one automatically.

   How to fix: Add a sitemap at /sitemap.xml (WordPress: Yoast or Rank Math generates it automatically; most platforms have a setting) and link it from your robots.txt.

7. 07
   MinorContent & SEO Readiness

   No llms.txt file found

   llms.txt is a new, simple file that tells AI assistants like ChatGPT what your business does and which pages matter most — making it easier for them to describe and recommend you accurately. It's optional today, but an easy edge while most sites don't have one.

   How to fix: Add a plain-text /llms.txt at the root of your site summarising your business and linking your key pages. RankAgent can generate one for you.

8. 08
   MinorContent & SEO Readiness

   No author or byline found

   This page doesn't say who wrote it. Google's E-E-A-T guidelines (Experience, Expertise, Authoritativeness, Trust) reward content with a credible, named author — and AI assistants weigh authorship when deciding what to trust and cite.

   How to fix: Add a visible byline and a short author bio with real credentials, and mark it up with author structured data.

9. 09
   MinorContent & SEO Readiness

   Question headings without a direct answer

   Your page poses questions in its headings but doesn't answer them concisely right below. AI assistants and Google's AI Overviews quote the short passage that directly resolves a question — a 1–3 sentence answer immediately under the heading — so a question with no tight answer beneath it rarely gets pulled.

   How to fix: Under each question heading, put a direct 1–3 sentence answer first, then expand. Lead with the answer, not the build-up.

• !No llms.txt file found
• ✓This page uses structured data
• !Question headings without a direct answer
• ✓This page uses question-style headings
• !No author or byline found
• ✓This page shows a date
• ✓This page includes data points

• ✓The page title is a good length
• ✓Social sharing preview is set up
• ✓This page tells Google which version is the main one
• ✓This page has exactly one main heading
• ✓The main heading is a good length
• ✓This page responded quickly (0.9s)
• ✓This page's code is a healthy size (331KB)
• ✓This page has a reasonable number of images
• ✓This page loads without a redirect chain
• ✓This page is set up to fit mobile screens
• ✓No fixed-width elements that break on mobile
• ✓This site uses a secure (HTTPS) connection
• ✓All content loads securely
• ✓This page has plenty of content (900 words)
• ✓This page links to other pages on the site (55)
• ✓This site has a favicon
• ✓Search engines are allowed to show this page