> For the complete documentation index, see [llms.txt](https://sitescanly.gitbook.io/sitescanly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitescanly.gitbook.io/sitescanly/fix-guides.md).

# Fix Guides

#### Practical fixes you can action, or forward to a developer

This section turns common SiteScanly findings into clear next steps. Each guide explains:

* What the issue means in plain English
* Why it matters (trust, enquiries, Google visibility, speed)
* The quickest fixes first
* When it’s a DIY job, and when to involve a developer

You do not need to fix everything at once. A solid approach is to pick **three fixes per month**, starting with anything that blocks enquiries or triggers trust warnings.

#### How to use these guides

1. Find the issue in your report (for example, “Broken links”)
2. Open the matching fix guide below
3. Start with the “Quick win” steps
4. If you use a developer, forward the “Developer steps” section with the affected page URLs

#### Fix guides included

* Fix broken links (404s)
* Fix redirect chains and loops
* Speed up slow mobile pages (quick wins)
* Optimise large images
* Add or fix page titles
* Add or fix meta descriptions
* Fix SSL and HTTPS issues
* Fix mixed content warnings
* Fix pages blocked from Google (indexing issues)
* Accessibility quick wins
* Check contact forms and key journeys


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sitescanly.gitbook.io/sitescanly/fix-guides.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.