Issue Nam Issue Type Issue PrioriURLs % of Total DescriptionHow To Fix

Images: MisIssue Low 13 0.23 Images thatInclude descriptive alt text for images to help users and th
URL: UppeWarning Low 13 0.22 URLs that hIdeally lowercase characters should be used for URLs onl
H1: Multipl Warning Medium 63 5.56 Pages which Consider updating the HTML to include a single <h1> on e
Meta DescrOpportunit Low 52 4.59 Pages which Consider updating the meta description to take advantage
Links: PageWarning Low 1 0.09 Pages that Review followed internal outlinks to ensure they provide g
Page TitlesOpportunit Medium 72 6.35 Pages which Write concise page titles to ensure important words are no
URL: Over Opportunit Low 4 0.07 URLs that aWhere possible use logical and concise URLs for users an
Pagination Warning High 1 0.09 The paginatEnsure paginated URLs are to canonical, indexable pages
Meta DescriOpportunit Low 29 2.56 Pages which It's important to write unique and descriptive meta descrip
Images: Al Opportunit Low 78 1.36 Images whic Write concise alt text that's helpful for users and search en
Meta DescriOpportunit Low 44 3.88 Pages which Update duplicate meta descriptions as necessary, so impo
H2: Multipl Warning Low 744 65.67 Pages which Ensure <h2>s are used in a logical hierarchical heading st
H1: Over 7 Opportunit Low 22 1.94 Pages which Write concise <h1>s for users, including target keywords w
Response CWarning Low 60 0.76 Internal URIdeally all internal links would be to canonical resolving UR
Meta DescrOpportunit Low 52 4.59 Pages which Consider updating the meta description to take advantage
H2: Missin Warning Low 325 28.68 Pages which Consider using logical and descriptive <h2>s on important
Page TitlesOpportunit Medium 52 4.59 Pages which Write concise page titles to ensure important words are no
Images: MisOpportunit Low 58 1.01 Image eleme Define all image sizes as their native size using width and
H1: Non-SeWarning Low 1 0.09 Pages with Ensure the <h1> is the first heading on the page. Heading
Page Title Opportunit Medium 156 13.77 Pages which Consider updating the page title to take advantage of the
Security: U Warning Low 1133 18.81 URLs that lConsider the benefits of including the rel="noopener" link
H2: Non-SeWarning Low 20 1.77 Pages with Ensure the <h2> is the second heading on the page. Head
URL: UndeOpportunit Low 5 0.08 URLs with Ideally hyphens should be used as word separators, rathe
Response CIssue High 1 0.01 Internal URMalformed URLs should be updated to the correct location
Images: OvOpportunit Medium 2249 39.11 Large image Uncompressed images bloat pages with unnecessary byte
URL: RepetWarning Low 1 0.02 URLs that hWhile not always an issue repetitive paths aren't particular
Images: MisIssue Low 1 0.02 Images thatInclude alt attributes with descriptive alt text for images to
Response Co Issue High 48 0.61 Internal URAll links on a website should ideally resolve to 200 'OK' UR
Page TitlesOpportunit Medium 111 9.8 Pages which Consider updating the page title to take advantage of the
Page TitlesOpportunit Medium 4 0.35 Pages which Update duplicate page titles as necessary, so each page c
Links: Inte Warning Low 865 76.35 Pages that Review the use of rel="nofollow" on internal links. These m
URL: Non AWarning Low 13 0.22 URLs with cURLs should be converted into a valid ASCII format, by en
Security: MWarning Low 5912 98.16 URLs that aSet a strict Content-Security-Policy response header acro
Security: MWarning Low 5912 98.16 URLs missin Consider setting a referrer policy of strict-origin-when-cros
H2: Duplic Opportunit Low 62 5.47 Pages which Update duplicate <h2>s as necessary, so important pages
H2: Over 7 Opportunit Low 35 3.09 Pages which Write concise <h2>s for users, including target keywords w
Response Co Warning Low 22 0.28 External URAll links on a website should ideally resolve to 200 'OK' UR
H1: Duplic Opportunit Low 48 4.24 Pages which Update duplicate <h1>s as necessary, so important pages
Security: Warning Low 5912 98.16 URLs that aThe HSTS header should be used across all pages to inst
Hreflang: MWarning Low 2 0.18 URLs missin Consider adding a fallback page for unmatched languages
Directives: Warning High 5 0.08 URLs contaiURLs with a 'noindex' should be reviewed carefully to ens
Security: P Warning Low 1133 18.81 URLs that lUpdate any resource links to be absolute links including th
Links: Inte Opportunit Low 1133 100 Pages that Review the missing anchor text outlinks and where approp
Response CWarning Low 320 4.07 External URMalformed URLs should be updated to the correct location
Page Title Opportunit Low 495 43.69 Page titles This is not necessarily an issue, but may point to a potent
Pagination Issue High 1 0.09 URLs contaiEnsure paginated URLs are linked to within <a> tags. This
CanonicalsWarning High 11 0.97 Pages that These URLs should be reviewed carefully to ensure the in
Pagination Issue Low 1 0.09 URLs that hEnsure paginated URLs contained within rel="next" or rel=
Meta DescrOpportunit Low 195 17.21 Pages which Write concise meta descriptions to ensure important word
Response CWarning High 2 0.03 Internal URReview URLs to ensure they should be disallowed. If they
URL: Para Warning Low 4 0.07 URLs that iWhere possible use a static URL structure without parame
Meta DescriOpportunit Low 137 12.09 Pages whichWrite concise meta descriptions to ensure important word
H1: Missin Issue Medium 9 0.79 Pages whichEnsure important pages have concise, descriptive and un
 ages to help users and the search engines understand them better. Where possible, decorative images should be provided using CSS bac
ould be used for URLs only. However, changing URLs is a big decision, and often it's not worth changing them for SEO purposes alone. If U
nclude a single <h1> on each page, and utilising the full heading rank between (h2 - h6) for additional headings.
cription to take advantage of the space left to include additional benefits, USPs or call to actions to improve click through rates (CTR).
to ensure they provide great usability to users navigating the website and unimportant pages are not being linked to unnecessarily.
re important words are not truncated in the search results, not visible to users and potentially weighted less in scoring.
concise URLs for users and search engines. However, changing URLs is a big decision, and often it's not worth changing them for SEO pur
anonical, indexable pages - so they can be crawled and indexed.
descriptive meta descriptions on key pages to communicate the purpose of the page to users, and entice them to click on your result over
ul for users and search engines - without keyword stuffing.
ons as necessary, so important pages contain a unique and descriptive title for users and search engines. If these are duplicate pages, then
cal hierarchical heading structure, and update where appropriate utilising the full heading rank between (h3 - h6) for additional headings.
ncluding target keywords where natural for users - without keyword stuffing.
to canonical resolving URLs, and avoid linking to URLs that redirect. This reduces latency of redirect hops for users, and enhanced efficien
cription to take advantage of the space left to include additional benefits, USPs or call to actions to improve click through rates (CTR).
iptive <h2>s on important pages that help the user and search engines better understand the page.
re important words are not truncated in the search results, not visible to users and potentially weighted less in scoring.
ative size using width and height attributes in the HTML. This allows the browser to calculate enough space for each image before it loads,
ing on the page. Headings should be in a logical sequential order from <h1> to <h6>. Review and update page heading levels so they are
to take advantage of the space left to include additional target keywords or USPs.
g the rel="noopener" link attribute on any links that contain the target="_blank" attribute to avoid security and performance issues for the us
eading on the page. Headings should be in a logical sequential order from <h1> to <h6>. Review and update page heading levels so they a
as word separators, rather than underscores. However, changing URLs is a big decision, and often it's not worth changing them for SEO pu
ated to the correct location and other connection issues can often be resolved by using different user-agents ('Config > User-Agent'), adjust
ges with unnecessary bytes, so ensure images are optimised with compression, properly scaled, and using the best image format to reduce
tive paths aren't particularly user friendly, or could be causing crawling issues if due to incorrect relative linking. Ideally any URL should be a
ptive alt text for images to help users and the search engines understand them better. Where possible, decorative images should be provide
ally resolve to 200 'OK' URLs. Errors such as a 404 or 410 should be updated to their correct locations, removed and redirected where appr
to take advantage of the space left to include additional target keywords or USPs.
necessary, so each page contains a unique and descriptive title for users and search engines. If these are duplicate pages, then fix the dup
on internal links. These might be valid to URLs that ideally wouldn't be crawled, or they could be by mistake. Remove the nofollow link attri
a valid ASCII format, by encoding links to the URL with safe characters (made up of % followed by two hexadecimal digits). Today browsers
cy response header across all page to help mitigate cross site scripting (XSS) and data injection attacks.
of strict-origin-when-cross-origin. It retains much of the referrer's usefulness, while mitigating the risk of leaking data cross-origins.
ssary, so important pages contain a unique and descriptive <h2> for users and search engines. If these are duplicate pages, then fix the d
ncluding target keywords where natural for users - without keyword stuffing.
ally resolve to 200 'OK' URLs. Errors such as 404 broken links should be updated so users are taken to the correct URL, or removed. A 403
ssary, so important pages contain a unique and descriptive <h1> for users and search engines. If these are duplicate pages, then fix the d
ed across all pages to instruct the browser that it should always request pages via HTTPS, rather than HTTP.
for unmatched languages, especially on language/country selectors or auto-redirecting homepages.
reviewed carefully to ensure they are correct and shouldn't be indexed. If these pages should be indexed, then the 'noindex' directive shou
absolute links including the scheme (HTTPS) to avoid security and performance issues.
outlinks and where appropriate include useful and descriptive anchor text to help users and search engines.
ated to the correct location and other connection issues can often be resolved by using different user-agents ('Config > User-Agent'), adjust
but may point to a potential opportunity to target alternative keywords, synonyms, or related key phrases.
ed to within <a> tags. This will allow them to be crawled and indexed, and pass PageRank onto any URLs they link to.
carefully to ensure the indexing and link signals are being consolidated to the correct URL. In a perfect world, a website wouldn't need to c
ed within rel="next" or rel="prev" attributes and within <a> tags are to the correct pages in the sequence.
to ensure important words are not truncated in the search results, and not visible to users.
ould be disallowed. If they are incorrectly disallowed, then the site's robots.txt should be updated to allow them to be crawled. Consider whe
L structure without parameters for key indexable URLs. However, changing URLs is a big decision, and often it's not worth changing them fo
to ensure important words are not truncated in the search results, and not visible to users.
ncise, descriptive and unique headings to help users, and enable search engines to score and rank the page for relevant search queries.
 provided using CSS background images or alternatively a null (empty) alt text should be provided (alt="") so that they can be ignored by as
SEO purposes alone. If URLs are changed, then appropriate 301 redirects must be implemented.

hrough rates (CTR).

hanging them for SEO purposes alone. If URLs are changed, then appropriate 301 redirects must be implemented.

o click on your result over the competition. It can also mean Google use this description for snippets in the search results for some queries,

are duplicate pages, then fix the duplicated pages by linking to a single version, and redirect or use canonicals where appropriate.
or additional headings.

ers, and enhanced efficiency for search engines.

ch image before it loads, avoiding large layout shifts.

ormance issues for the users of legacy browsers that may visit the website.
e heading levels so they are descending in order, for example the heading element following an <h1> should be an <h2>, rather than an <h
changing them for SEO purposes alone. If URLs are changed, then appropriate 301 redirects must be implemented.
fig > User-Agent'), adjusting the crawl speed ('Config > Speed') or disabling firewalls & proxies.
st image format to reduce file size where possible.
eally any URL should be as concise as possible. However, changing URLs is a big decision, and often it's not worth changing them for SEO
images should be provided using CSS background images or alternatively a null (empty) alt text should be provided (alt="") so that they can
and redirected where appropriate. A 403 forbidden error occurs when a web server denies access to the SEO Spider's request and can ofte

e pages, then fix the duplicated pages by linking to a single version, and redirect or use canonicals where appropriate.
move the nofollow link attribute to important URLs you wish to be crawled, indexed and receive PageRank.
al digits). Today browsers and the search engines are largely able to transform URLs accurately.

ata cross-origins.
cate pages, then fix the duplicated pages by linking to a single version, and redirect or use canonicals where appropriate.

t URL, or removed. A 403 forbidden error occurs when a web server denies access to the SEO Spider's request and can often be resolved
cate pages, then fix the duplicated pages by linking to a single version, and redirect or use canonicals where appropriate.

e 'noindex' directive should be removed.

fig > User-Agent'), adjusting the crawl speed ('Config > Speed') or disabling firewalls & proxies. If they can be viewed in a browser, then it's

website wouldn't need to canonicalise any URLs as only canonical versions would be linked to internally on a website, but often they are req

be crawled. Consider whether you should be linking internally to these URLs and remove links where appropriate.
ot worth changing them for SEO purposes alone. If URLs are changed, then appropriate 301 redirects must be implemented.

elevant search queries.

results for some queries, rather than make up their own based upon the content of the page.

here appropriate.

uld be followed by an <h2>.

n <h2>, rather than an <h3>.

th changing them for SEO purposes alone. If URLs are changed, then appropriate 301 redirects must be implemented.
ed (alt="") so that they can be ignored by assistive technologies, such as screen readers.
der's request and can often be resolved by switching the user-agent to Chrome via 'Config > User-Agent' and crawling again.

nd can often be resolved by switching the user-agent to Chrome via 'Config > User-Agent'. If they can be viewed in a browser, then it's ofte

wed in a browser, then it's often not an issue.

site, but often they are required due to various circumstances outside of control, and to prevent duplicate content. Update internal links to ca
in a browser, then it's often not an issue.

Update internal links to canonical versions of URLs where possible.