A website can look professional on the surface and still have problems that stop it from getting traffic, enquiries, leads or sales. A page may be live but not indexed. A service page may rank but get no clicks. A contact form may look fine on desktop but fail on mobile. That is why a proper website audit matters.
This guide explains how to do a website audit step by step, especially for freelancers, developers and software houses who need to check websites, find issues, explain them clearly, and turn the findings into practical fixes.
You can also run a quick scan using the Website Audit Tool to check common website issues before starting a deeper manual review.
What Is a Website Audit?
A website audit is a complete review of a website’s health, structure, content, performance, usability, security and conversion setup. The goal is to find what is broken, what is weak, what is stopping growth, and what should be fixed first.
A useful audit does not just say, “This page has issues.” It explains what the issue is, why it matters, which page is affected, and what action is needed.
Simple definition
A website audit is a step-by-step inspection of a website to find technical, content, user experience, performance, tracking and conversion problems.
Example
If a website has 50 service pages but only 10 are indexed, the audit should find why those pages are missing from search results. The issue could be a noindex tag, poor internal linking, sitemap problems, blocked crawling, duplicate pages or weak content.
Why Website Audits Matter for Freelancers, Developers and Software Houses
For freelancers, developers and software houses, a website audit is not just a checklist. It is a way to understand the real condition of a website before quoting work, starting a redesign, launching a project or selling ongoing maintenance.
For freelancers
A freelancer can use a website audit before quoting a redesign, content improvement, performance fix or monthly support package.
Example: A client asks for help because their website gets no enquiries. After auditing, you find the contact form is broken on mobile, the main service page has no clear call to action, and blog posts are not linking to service pages. Now you can quote based on actual problems instead of guessing.
For developers
Developers can use audits to catch launch problems such as staging links, oversized images, missing redirects, poor mobile layout, broken forms and tracking errors.
Example: A developer launches a new WordPress site. The audit finds that the staging noindex tag is still active, images are too large, and the sitemap contains old demo pages. These are common issues that can hurt a site if no one checks them.
For software houses
A software house can use website audits as part of project discovery, monthly retainers, technical support, website maintenance and conversion improvement services.
Instead of telling a client, “Your website needs improvement,” you can show clear findings, priorities and a practical fix plan.
Website Audit vs SEO Audit: What Is the Difference?
A website audit is wider than an SEO audit. An SEO audit focuses mainly on search visibility, while a full website audit also checks speed, UX, security, content, tracking and conversions.
| Audit Type | Main Focus | Example Checks |
|---|---|---|
| Website audit | Overall website health | Speed, UX, security, forms, tracking, content, links and technical issues |
| SEO audit | Search performance | Indexing, titles, meta descriptions, keywords, internal links and backlinks |
| Technical audit | Website structure and access | Robots.txt, sitemap, redirects, canonical tags, status codes and crawl issues |
| Content audit | Content quality | Thin pages, outdated content, missing FAQs, duplicate content and weak page structure |
| Conversion audit | Leads, sales and enquiries | CTAs, forms, checkout, phone links, trust signals and landing pages |
Key Terms You Should Know Before Doing a Website Audit
| Term | Meaning |
|---|---|
| Crawlability | Whether search engines and audit tools can access and move through the website. |
| Indexability | Whether a page is allowed to appear in search results. |
| Robots.txt | A file that gives crawl instructions to search engines and bots. |
| XML sitemap | A file that lists important website URLs for search engines to discover. |
| Title tag | The page title shown in browser tabs and often in search results. |
| Meta description | A short page summary that may appear in search results. |
| H1 tag | The main visible heading of a page. |
| Canonical tag | A tag that tells search engines which version of a page is the preferred version. |
| Redirect | A rule that sends users and crawlers from one URL to another. |
| 404 error | A missing page error. |
| Core Web Vitals | Performance metrics related to loading speed, responsiveness and visual stability. |
| Internal links | Links between pages on the same website. |
| Schema markup | Structured data that helps search engines understand page content. |
| CTA | Call to action, such as “Get a Quote”, “Book a Call” or “Run a Website Audit”. |
What Should a Website Audit Include?
A complete website audit should cover the main areas that affect how people and search engines experience the site.
- Technical structure
- Crawlability and indexability
- Website speed and Core Web Vitals
- On-page optimisation
- Content quality
- Internal linking
- Mobile usability
- Navigation and user experience
- Conversion paths
- Security and maintenance
- Analytics and tracking
- Competitor comparison
- Schema and structured data
- Final priority list and action plan
The point is not to fix everything at once. The point is to find what matters most and create a clear order of work.
Example: A broken contact form is more urgent than one missing image alt tag. A key page blocked from indexing is more urgent than a slightly long title tag.
How to Do a Website Audit Step by Step
Step 1: Define the Goal of the Audit
Do not start by opening tools. First, decide what problem the audit needs to solve.
| Audit Goal | What to Check First |
|---|---|
| Website has no traffic | Indexing, sitemap, keywords, content quality and internal links |
| Website has impressions but no clicks | Title tags, meta descriptions, rankings and search intent |
| Website has traffic but no leads | CTAs, forms, landing pages, trust signals and tracking |
| Website is slow | Images, scripts, hosting, caching and Core Web Vitals |
| Website was redesigned | Redirects, broken links, indexing, sitemap and analytics tracking |
| Ecommerce sales are low | Product pages, category pages, checkout, filters, speed and trust signals |
Example: If a software agency client says, “We launched our new website three months ago but enquiries are low,” the audit should check more than rankings. It should review landing pages, forms, CTAs, mobile layout, trust signals and tracking.
Step 2: Run a Quick Website Health Check
Start with a quick scan to catch obvious issues. You can use the Website Audit Tool to review public website signals such as technical health, links, security, performance and structured data.
You can also use the Website SEO Score Checker to review common website visibility and technical signals.
Record your findings in a simple table
| URL | Issue | Category | Severity | Fix Needed |
|---|---|---|---|---|
| /services/ | Missing meta description | On-page | Medium | Write a unique description |
| /contact/ | Form not working on mobile | Conversion | Critical | Fix form validation and test again |
| /pricing/ | Slow mobile load | Performance | High | Compress images and delay non-critical scripts |
Step 3: Crawl the Website
A website crawl helps you see how the site is structured and where technical problems exist.
Check for these crawl issues
- Broken pages
- Redirect chains
- Duplicate URLs
- Missing title tags
- Duplicate title tags
- Missing meta descriptions
- Missing or repeated H1 tags
- Thin pages
- Orphan pages
- Canonical issues
- Pages blocked from indexing
- Internal links pointing to 404 pages
Example: A 70-page website may have 18 duplicate title tags, 12 missing meta descriptions, 9 old internal links and one key landing page marked as noindex. The noindex issue should be fixed first because it can stop the landing page from appearing in search results.
Step 4: Check Indexing and Crawlability
A page cannot bring organic traffic if search engines cannot discover, crawl or index it.
What to check
- Is the homepage indexed?
- Are important service pages indexed?
- Are important blog posts indexed?
- Is the XML sitemap available?
- Are important pages blocked by robots.txt?
- Are important pages marked as noindex?
- Are canonical tags correct?
- Are redirects working properly?
- Are important pages linked internally?
Check the robots.txt file by opening:
https://example.com/robots.txtA dangerous robots.txt rule may look like this:
User-agent: *
Disallow: /This can block the full website from being crawled. If you need to create or review crawler rules, use the Robots.txt Generator.
You should also check the sitemap:
https://example.com/sitemap.xmlA sitemap should include important public pages and avoid broken, redirected, private or duplicate URLs. You can create a clean sitemap using the XML Sitemap Generator.
Step 5: Audit Website Speed and Core Web Vitals
A slow website creates friction. People may leave before the page loads, especially on mobile.
| Area | What to Look For |
|---|---|
| Images | Oversized images, missing compression and poor file formats |
| JavaScript | Too many scripts, unused files and render-blocking code |
| CSS | Unused CSS and large stylesheets |
| Fonts | Too many font files or slow external loading |
| Hosting | Slow server response time |
| Caching | No browser caching or server caching |
| Third-party scripts | Heavy chat widgets, tracking scripts, ads or embeds |
Core Web Vitals to check
| Metric | What It Means |
|---|---|
| Largest Contentful Paint | How fast the main content loads |
| Interaction to Next Paint | How responsive the page feels when users interact |
| Cumulative Layout Shift | Whether the layout jumps while loading |
Real example: A homepage takes six seconds to load on mobile because the hero image is 3.8 MB, a slider plugin loads on every page, and multiple tracking scripts load before the main content.
The fix is to compress the image, remove the slider if it is not needed, delay non-critical scripts, optimise fonts and enable caching.
Step 6: Audit On-Page Elements
On-page checks help you see whether each page clearly communicates its topic and purpose.
What to check
- Title tag
- Meta description
- H1 heading
- H2 and H3 structure
- URL structure
- Keyword targeting
- Search intent
- Internal links
- Image alt text
- Schema markup
- Duplicate titles
- Duplicate descriptions
Title tag example
Weak title: Home
Better title: Website Design and Development Services for Small Businesses
H1 example
Weak H1: Welcome to Our Website
Better H1: Custom Website Development for Startups and Small Businesses
Meta description example
Weak description: We provide the best services. Contact us today.
Better description: Need a fast, mobile-friendly business website? Our developers build websites with clear pages, contact forms, analytics tracking and easy content editing.
Step 7: Audit Content Quality and Search Intent
Content quality is not just about word count. A page should answer the reason someone searched in the first place.
| Question | Why It Matters |
|---|---|
| Does the page answer the main query? | Weak answers lose visitors quickly. |
| Is the content outdated? | Old advice can become inaccurate. |
| Is the page too thin? | Thin pages may not satisfy the visitor. |
| Does it include examples? | Examples make the content easier to apply. |
| Does it include FAQs? | FAQs answer common follow-up questions. |
| Does it link to related pages? | Internal links help visitors and crawlers find useful pages. |
Example of weak service page copy:
We build modern websites for all kinds of businesses.
Better version:
We build fast, mobile-friendly WordPress websites for small businesses that need clear service pages, contact forms, analytics tracking and easy content editing.
The better version is clearer because it explains the audience, platform, benefits and deliverables.
Step 8: Audit Internal Links and Site Structure
Internal links help people and search engines move through the website. Poor internal linking can hide important pages.
What to check
- Are important pages linked from the homepage?
- Are service pages linked from the main navigation?
- Do blog posts link to relevant tools or service pages?
- Do old posts link to newer useful content?
- Are there internal links pointing to broken pages?
- Are important pages too many clicks away from the homepage?
- Is anchor text clear?
Useful internal links for this topic
- Run a website audit
- Check website score
- Generate an XML sitemap
- Create a robots.txt file
- Check domain authority
- Format FAQs
- Generate schema markup
Avoid vague anchor text like “click here.” Use clear anchor text such as “run a website audit” or “generate an XML sitemap.”
Step 9: Audit Mobile Usability and User Experience
A website may look fine on desktop and still fail on mobile. Always test the website on a real mobile device.
Manual mobile test
- Find the main service page.
- Open a blog post.
- Click a call-to-action button.
- Submit a contact form.
- Tap the phone or email link.
- Move from a blog post to a service page.
- Open and close the mobile menu.
| UX Area | What to Look For |
|---|---|
| Navigation | Is the menu simple and easy to use? |
| Layout | Is the page easy to scan? |
| Fonts | Is the text readable on mobile? |
| Buttons | Are buttons large enough to tap? |
| Forms | Are forms short and easy to complete? |
| CTAs | Are important calls to action visible? |
| Popups | Do popups block important content? |
Step 10: Audit Conversions and Lead Generation
Traffic is useful, but traffic without action is limited. A conversion audit checks whether the website turns visitors into enquiries, sales, sign-ups or bookings.
What to check
- Are CTAs clear?
- Are buttons visible above the fold?
- Does each important page have one main action?
- Are forms working?
- Are forms too long?
- Are phone and email links clickable?
- Are trust signals visible?
- Are testimonials included?
- Are case studies easy to find?
- Are conversion events tracked?
Weak CTA examples
- Submit
- Click here
- Learn more
- Get started
Better CTA examples
- Request a Free Website Audit
- Book a Website Review
- Get a Website Fix Quote
- Check My Website Health
Example: A freelancer gets traffic from blog posts, but those posts do not link to any service page. The audit should recommend relevant internal links and stronger CTAs inside the articles.
Step 11: Audit Website Security and Maintenance
Security and maintenance issues can affect trust, reliability, speed and business risk.
| Security Item | What to Review |
|---|---|
| HTTPS | Does the full site load securely? |
| SSL certificate | Is the certificate valid and not expired? |
| CMS version | Is the platform updated? |
| Plugins | Are unused or outdated plugins installed? |
| Admin users | Are old admin accounts still active? |
| Backups | Are backups running and restorable? |
| Forms | Are forms protected from spam? |
| Error logs | Are there repeated server errors? |
You can also review website strength and competitor comparison signals using the Domain Authority Checker.
Step 12: Check Analytics, Tracking and Reporting
Before making conclusions, check whether the website is tracking important actions correctly.
What to check
- Is analytics installed?
- Is Search Console connected?
- Are form submissions tracked?
- Are phone clicks tracked?
- Are email clicks tracked?
- Are ecommerce purchases tracked?
- Are thank-you pages working?
- Are duplicate tracking tags installed?
- Are campaign links tracked properly?
- Are monthly reports reviewed?
Example: A client may say the website does not generate leads, but the real problem could be broken tracking. Always confirm the data before making recommendations.
Step 13: Compare Competitors
A competitor comparison helps you understand what other websites are doing better. Do not copy competitors. Use the comparison to find gaps.
| Area | Your Site | Competitor Site | Opportunity |
|---|---|---|---|
| Service pages | 3 short pages | 8 detailed pages | Build stronger service pages |
| Blog content | No guides | 20 useful guides | Add educational content |
| Case studies | None | 6 case studies | Add proof of work |
| FAQs | Missing | Detailed FAQs | Add helpful FAQ sections |
| Internal links | Weak | Strong | Improve page connections |
Step 14: Check Schema Markup and Structured Data
Schema markup helps search engines understand the content and structure of a page.
| Schema Type | Use |
|---|---|
| BlogPosting | Marks the page as a blog article. |
| BreadcrumbList | Shows the page hierarchy. |
| FAQPage | Marks common questions and answers. |
| WebSite with SearchAction | Defines the website and its search function. |
| WebApplication | Useful for describing a web-based audit tool. |
You can create structured data using the Schema Generator and prepare FAQ content using the FAQ Formatter.
How to Prioritize Website Audit Issues
A website audit can find dozens or even hundreds of issues. The important part is knowing what to fix first.
| Priority | Type of Issue | Example | What to Do |
|---|---|---|---|
| Critical | Blocks users or search engines | Broken contact form, blocked pages, expired SSL | Fix immediately |
| High | Affects traffic, leads or revenue | Slow service pages, weak titles, broken checkout | Fix this month |
| Medium | Improves performance | Weak internal links, thin content, missing FAQs | Add to roadmap |
| Low | Minor cleanup | Slightly long title tag, small layout issue | Fix when convenient |
Impact vs Effort Model
| Impact | Effort | Decision |
|---|---|---|
| High | Low | Fix first |
| High | High | Plan properly |
| Low | Low | Batch together |
| Low | High | Avoid unless necessary |
Example: If an audit finds a broken contact form, a missing meta description and 20 images without alt text, fix the contact form first. It directly affects leads.
Website Audit Checklist
Technical and Crawlability Checklist
- Check HTTPS.
- Check robots.txt.
- Check XML sitemap.
- Check indexability.
- Check canonical tags.
- Check redirects.
- Check 404 pages.
- Check server errors.
- Check duplicate URLs.
- Check internal linking depth.
On-Page Checklist
- Review title tags.
- Review meta descriptions.
- Check H1 headings.
- Check H2 and H3 structure.
- Review URL structure.
- Check image alt text.
- Check keyword targeting.
- Check search intent.
- Add internal links.
- Review schema markup.
Content Checklist
- Find thin pages.
- Find outdated content.
- Check duplicate content.
- Add missing FAQs.
- Improve weak service pages.
- Add examples.
- Add case studies.
- Improve topic coverage.
- Remove or merge poor pages.
- Refresh useful old pages.
Speed and UX Checklist
- Test mobile speed.
- Compress images.
- Remove unused scripts.
- Check Core Web Vitals.
- Test mobile menu.
- Test forms.
- Review CTAs.
- Check popups.
- Improve readability.
- Check basic accessibility.
Conversion and Tracking Checklist
- Test contact forms.
- Test phone links.
- Test email links.
- Check checkout if ecommerce.
- Review CTA placement.
- Add trust signals.
- Check analytics setup.
- Check Search Console setup.
- Track conversions.
- Create a fix priority list.
Best Tools for Doing a Website Audit
Tools help you find issues faster, but the real value comes from understanding what the data means and what should be fixed first.
| Task | Useful Tool |
|---|---|
| Quick website audit | Website Audit Tool |
| Website score check | Website SEO Score Checker |
| Sitemap creation | XML Sitemap Generator |
| Robots.txt setup | Robots.txt Generator |
| Domain strength review | Domain Authority Checker |
| Structured data | Schema Generator |
| FAQ formatting | FAQ Formatter |
How to Present a Website Audit Report to a Client
A client does not need a confusing list of every warning from every tool. They need clear findings, business impact and recommended actions.
A good audit report should include
- Executive summary
- Top issues
- Screenshots
- Severity levels
- Business impact
- Recommended fixes
- Estimated effort
- Priority order
- Tools used
- 30-day action plan
| Issue | Page URL | Severity | Why It Matters | Recommended Fix | Owner |
|---|---|---|---|---|---|
| Contact form fails on mobile | /contact/ | Critical | Leads may not submit enquiries | Fix form validation and test on mobile | Developer |
| Page not indexed | /services/ | Critical | Page cannot appear in search results | Remove noindex and submit URL | Developer |
| Slow mobile page | /web-design/ | High | Users may leave before reading | Compress images and delay scripts | Developer |
| Weak title tag | /software-development/ | Medium | May reduce clicks | Rewrite title around page topic | Content team |
30-Day Website Audit Action Plan
Week 1: Fix Critical Technical Issues
- Fix broken contact forms.
- Fix SSL or HTTPS issues.
- Fix major 404 errors.
- Fix bad redirects.
- Remove accidental blocking rules.
- Remove noindex from important pages.
- Update sitemap errors.
- Fix broken checkout pages.
Week 2: Improve Page Foundations
- Rewrite weak title tags.
- Rewrite weak meta descriptions.
- Improve H1 headings.
- Add internal links.
- Fix canonical tags.
- Improve URL structure where needed.
- Add useful schema markup.
Week 3: Improve Content and UX
- Improve thin service pages.
- Refresh outdated blog posts.
- Add missing FAQs.
- Improve CTAs.
- Add testimonials or proof.
- Compress large images.
- Improve mobile readability.
Week 4: Measure and Report
- Check indexed pages.
- Review impressions.
- Review click-through rate.
- Check organic traffic.
- Review leads and form submissions.
- Test page speed again.
- Create the next month’s roadmap.
Common Website Audit Mistakes to Avoid
1. Sending an automated report without explaining it
Automated reports can help, but clients need interpretation. Explain what matters, why it matters and what should be fixed first.
2. Treating every issue as urgent
Not every warning deserves immediate attention. A broken form is urgent. One missing alt tag on a decorative image is not.
3. Auditing only the homepage
Important problems often exist on service pages, product pages, blog posts, landing pages and contact pages.
4. Ignoring mobile
Always test mobile navigation, forms, buttons, spacing and page speed.
5. Ignoring search intent
A page may include the right keyword but still fail if it does not answer what visitors actually want.
6. Forgetting conversion tracking
You cannot judge performance properly if forms, calls and key actions are not tracked.
7. Giving problems without a plan
A useful audit ends with a clear action plan, not just a list of problems.
FAQs About Website Audits
How do I do a website audit?
Start by defining the goal of the audit. Then check crawlability, indexing, speed, page structure, content quality, mobile usability, security, tracking and conversions. After that, prioritise the findings by impact and effort.
What is included in a website audit?
A website audit usually includes technical checks, indexing, sitemap review, robots.txt review, speed testing, content review, internal links, mobile usability, security, analytics tracking and conversion checks.
What is the difference between a website audit and an SEO audit?
A website audit reviews the full health of a site, including performance, UX, content, security, tracking and conversions. An SEO audit focuses mainly on search visibility, indexing, page structure, links and keyword performance.
Can I do a website audit for free?
Yes. You can do a basic audit using free tools, manual checks and browser testing. For deeper audits, you may need crawling tools, analytics access and performance testing tools.
What should I fix first after a website audit?
Fix critical issues first. These include broken forms, blocked pages, noindex tags on important pages, SSL problems, checkout errors, serious redirect issues and pages that cannot be crawled or indexed.
How often should I audit a website?
A small business website should be audited every few months. You should also audit after a redesign, migration, hosting change, content restructure, traffic drop or major technical update.
Should developers offer website audits to clients?
Yes. Website audits help developers find performance, mobile, security, technical and tracking issues. They can also support maintenance plans, speed fixes and post-launch improvements.
What should a client audit report include?
A client audit report should include a summary, top issues, affected URLs, severity, screenshots, business impact, recommended fixes, estimated effort, responsible person and a clear action plan.
Final Thoughts
A website audit should not be a random list of warnings. It should help you understand what is stopping a website from getting more traffic, better engagement and more enquiries.
For freelancers, developers and software houses, the real value is not just finding problems. The value is knowing which problems matter, explaining them clearly, and turning them into a practical fix plan.
Start with the goal, check the technical foundation, review the content, test the mobile experience, confirm tracking and then prioritise the work. That is how to do a website audit that actually helps.
To begin, try the Website Audit Tool and use the checklist above to review the results properly.