Report loading
mindsenap.figma.site
Preparing the full page inventory and screenshots.
Report loading
Preparing the full page inventory and screenshots.
49 / 100
Poor
0 critical fixes · 5 quick wins
Priority verdict
49/100 - poor. Start with the fixes below before reading the full report.
The biggest issue is page is set to 'noindex' (google search essentials). Start with the priority fixes, then use the evidence and technical details when a developer needs proof.
Poor
3 priority fixes identified
Score
49 / 100 — Poor
No major launch blockers found.
Biggest risk
Page is set to 'noindex' (Google Search Essentials)
how search engines understand the page
Fastest win
Page is set to 'noindex' (Google Search Essentials)
A practical first fix for your builder or AI agent.
Estimated impact
Higher confidence and discoverability
Fix the priority items first, then re-scan to confirm the evidence.
Biggest area to improve: Security, which mostly means visitor safety and trust.
Priority verdict
This site is technically inspectable, but the priority is making the next fix obvious.
Fix the highest-impact issue first, then use structured evidence and developer prompts so search engines, AI answer engines, and real visitors can understand the site more reliably.
What's working
What needs attention
What to do first
The MINDS website is currently invisible to search engines due to a high-priority configuration error that prevents organic discovery.
The site demonstrates strong brand identity and user experience fundamentals. The visual hierarchy is professional, utilizing a consistent pastel palette and bold typography that establishes immediate authority. On both desktop and mobile, the hero section provides a clear value proposition and effective primary calls-to-action that guide users through the service journey. Furthermore, the site shows technical maturity in its performance optimizations, specifically through the use of responsive images and lazy loading to manage page weight.
However, the most significant weakness is a high-priority SEO failure: the homepage is explicitly set to noindex. This directive instructs search engines to exclude the site from all search results, rendering the entire digital presence non-existent for organic traffic. This issue is compounded by a serious security concern regarding the absence of a Content-Security-Policy (CSP), which leaves the site vulnerable to cross-site scripting (XSS) and injection attacks.
The biggest opportunity lies in optimizing the site for the emerging AI-search ecosystem. While the site is technically accessible to AI crawlers, it lacks the structured data and specific content depth—such as FAQs or product catalogues—required to be cited effectively by answer engines. Implementing JSON-LD structured data and expanding content to answer specific user prompts will position MINDS as a primary source for AI-driven discovery.
To restore visibility and secure the platform, the following actions are required in the first 30 days:
noindex meta tag from the homepage to allow search engine indexing.Scan details
Checks performed: SEO, UX, accessibility, performance, security, AI search.
Fix workflow
Treat this report as a queue: send the ready fixes, accept any intentional risks, then re-scan the production URL after changes land.
35
Ready to send
56
Not started
0
Accepted risk
0
Re-scan queued
The full report has all the proof. This is the owner-friendly version of what to do first.
Plain-English reason
This affects how search engines understand the page. PageLens marked it as important so you know where it belongs in the queue.
What to ask your builder or AI agent to do
If this page is intended to be public and discoverable via search engines, remove the `<meta name="robots" content="noindex">` tag from the `<head>` section.
The page contains a `<meta name="robots" content="noindex">` tag. This instructs search engines not to include this page in their search results, which prevents organic discovery.
Plain-English reason
This affects visitor safety and trust. PageLens marked it as important so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Add a Content-Security-Policy header. Start restrictive: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'
No CSP header found. The site is vulnerable to XSS and injection attacks.
Plain-English reason
This affects whether everyone can use the site. PageLens marked it as important so you know where it belongs in the queue.
What to ask your builder or AI agent to do
Element matching `.css-6zw8rt.css-jpsr3q[href$="preparacao"] > .css-6zw8rt.css-jpsr3q[href$="preparacao"]` has contrast ratio 4.35; WCAG AA requires 4.5:1. Increase the contrast between foreground and background colours (the Tailwind hint below proposes the next darker step in the same family if the offending class is a recognised palette utility). Reference: https://dequeuniversity.com/rules/axe/4.11/color-contrast?application=playwright
Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds. Fix any of the following: Element has insufficient color contrast of 4.35 (foreground color: #8f54e7, background color: #e7fff3, font size: 11.3pt (15.083px), font weight: normal). Expected contrast ratio of 4.5:1
A practical roadmap for turning the audit into progress.
Today
If this page is intended to be public and discoverable via search engines, remove the `<meta name="robots" content="noindex">` tag from the `<head>` section.
This week
Remove the `<meta name="robots" content="noindex">` tag from the `<head>` section if you want this page to be indexed by Google.
This month
Add a Content-Security-Policy header. Start restrictive: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'
Same data as the full report, grouped by what a non-technical owner should do with it.
High-impact fixes that should usually be tackled before anything else.
Important fixes that may need more development time or a design decision.
Nothing in this bucket.
Polish and lower-priority work. Useful, but not where to start.
Need the detail?
The full report still has every finding, evidence, rule ID, filters, screenshots, and technical panels.