Most important first.
Always-secure instruction (HSTS)
Domain & Security
Technical
Your site does not tell browsers to always use the secure connection.
Why it matters: Without this instruction, a browser may still try the insecure address first, which leaves room for the connection to be tampered with.
How to fix it: Ask your developer or host to add the Strict-Transport-Security header once HTTPS works on every page.
Email sender record (SPF)
Domain & Security
Moderate
Your domain does not publish an SPF record, so mail servers cannot tell which senders are genuinely yours.
Why it matters: Without it, your own emails are more likely to land in spam, and others find it easier to send mail that claims to come from you.
How to fix it: Add an SPF record in your domain's DNS settings; your email provider publishes the exact line to use.
Email protection policy (DMARC)
Domain & Security
Moderate
Your domain does not publish a DMARC record, which lets anyone send email that claims to come from your domain.
Why it matters: A DMARC policy tells receiving mail servers what to do with mail that fails your checks, which protects your customers and your inbox placement.
How to fix it: Add a DMARC record in your DNS, starting with a monitoring policy, then tighten it once your legitimate mail passes.
Address findable
AI Readiness
Quick
We found no street address on your homepage.
Why it matters: A visible address tells customers and AI assistants where you are, and matches you to your Google listing.
How to fix it: Add your street address to the homepage, in the same form as on your Google listing.
Link preview when shared
AI Readiness
Quick
Your homepage is missing the tags that make a full preview when it is shared.
Why it matters: When someone shares your link, these tags decide the picture, title and description people see in the post.
How to fix it: Add Open Graph tags (title, description and image); most website builders have a social sharing setting for this.