Export Report
OVERALL SCORE
Level 2, Agent-Limited
- AI Discoverability 45 out of 100
- Agent Ease of Use 53 out of 100
- Security & Trust 78 out of 100
- GEO, AIO and AEO 63 out of 100
- SEO 85 out of 100
- Performance 69 out of 100
- Accessibility 0 out of 100
What AI sees of your website
Income Tax Software: TaxCloud India | ITR Filing Software for Chartered Accountants & Tax Professionals
TaxCloud is a web-based Income Tax Return (ITR) filing software for CAs, accountants, tax professionals and corporations in India. TaxCloudIndia works fast, secure, and a user-friendly platform that is trusted by thousands of chartered acc...
Next step
Turn this report into a fix workflow
3 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.
| Metric | Score | Status | Passed | Failed | Warning | Evidence |
|---|---|---|---|---|---|---|
| AI Discoverability | 45 | Priority fix | 20 | 4 | 2 | View details |
| Discoverability | 47 | Priority fix | 6 | 0 | 0 | |
| Content Readiness | 42 | Priority fix | 13 | 3 | 2 | View details |
| Bot Access Control | 45 | Priority fix | 1 | 1 | 0 | View details |
| Agent Ease of Use | 53 | Needs work | 6 | 0 | 0 | |
| API | 50 | Needs work | 4 | 0 | 0 | |
| Google Agentic Browsing | 67 | Needs work | 2 | 0 | 0 | |
| GEO, AIO and AEO | 63 | Needs work | 7 | 0 | 0 | |
| GEO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AIO Readiness | Not Applicable | Not Applicable | 2 | 0 | 0 | |
| AEO Readiness | Not Applicable | Not Applicable | 3 | 0 | 0 | |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| SEO | 85 | Mostly ready | 8 | 0 | 0 | |
| Security & Trust | 78 | Mostly ready | 19 | 1 | 2 | View details |
| Security & Trust | 78 | Mostly ready | 19 | 1 | 2 | View details |
| Performance | 69 | Needs work | 12 | 0 | 0 | |
| Performance | 69 | Needs work | 12 | 0 | 0 |
Prioritized recommendations
Issues ranked by score impact
3 items need attention
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
75 Fail
AI DiscoverabilityContent ReadinessEstablished
Content freshness signals
Content freshness signals is missing or incomplete.
Needs attention
Content freshness signals
Issue
Content freshness signals are invalid: json-ld datePublished is not a parseable date ().; json-ld dateModified is not a parseable date ()..
Details
Why it matters
Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.
Check name
Content freshness signals
Score
25/100
Status
fail
Category
Content Readiness
Maturity
Established
Goal
Expose modified and published dates for freshness-aware retrieval, citation, and ranking.
Result
Content freshness signals is missing or incomplete.
Validation steps
Validate Last-Modified header
No valid Last-Modified HTTP header was found.
Last-Modified freshness signal is missing or invalid
Validate structured freshness dates
No Schema.org freshness dates were found.
Structured freshness dates are missing or invalid
Validate metadata freshness dates
No Open Graph, Dublin Core, or generic meta freshness date was found.
Metadata freshness dates are missing or invalid
Corroborate with sitemap lastmod
Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.
Sitemap lastmod corroboration is missing
Check date validity and consistency
json-ld datePublished is not a parseable date ().; json-ld dateModified is not a parseable date ().
Freshness dates are invalid or inconsistent
Evidence log5 steps · 20 lines
Validate Last-Modified header [fail]! No valid Last-Modified HTTP header was found.INFOValidate Last-Modified headerINFOReading Last-Modified response headerFAILCheck Last-Modified header is present and parseable actual="missing" expected="valid" alternateDates=[]FAILLast-Modified header is missing or invalidValidate structured freshness dates [warning]! No Schema.org freshness dates were found.INFOValidate structured freshness datesINFOCollecting Schema.org freshness dates from JSON-LD, Microdata, and RDFaWARNCheck structured freshness date count actual=2 expected="> 0" invalidDateCount=2 formats={"json-ld":2} alternateDates=[]WARNStructured freshness dates include invalid values invalidDateCount=2Validate metadata freshness dates [fail]! No Open Graph, Dublin Core, or generic meta freshness date was found.INFOValidate metadata freshness datesINFOCollecting Open Graph, Dublin Core, and generic meta freshness datesFAILCheck metadata freshness date count actual=0 expected="> 0" metaDateCount=0 invalidDateCount=0 alternateDates=[]FAILNo metadata freshness dates foundCorroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=13 attempts=8WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=8Check date validity and consistency [fail]! json-ld datePublished is not a parseable date ().; json-ld dateModified is not a parseable date ().INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=2 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"json-ld datePublished is not a parseable date ()."},{"severity":"fail","message":"json-ld dateModified is not a parseable date ()."}]FAILInvalid freshness date issue found issues=["json-ld datePublished is not a parseable date ().","json-ld dateModified is not a parseable date ()."]
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
69 Fail
AI DiscoverabilityBot Access ControlEstablished
AI bot rules in robots.txt
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Needs attention
AI bot rules in robots.txt
Issue
No explicit User-agent rules were found for major AI crawler tokens.
Details
Why it matters
AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.
Check name
AI bot rules in robots.txt
Score
31/100
Status
fail
Category
Bot Access Control
Maturity
Established
Goal
Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.
Result
AI bot rules in robots.txt failed at "Classify AI crawler rules".
Validation steps
Classify AI crawler rules
No explicit User-agent rules were found for major AI crawler tokens.
robots.txt lacks explicit AI crawler rules
Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate script execution".
35 Fail
Security & TrustSecurity & TrustEstablished
Content-Security-Policy
Content-Security-Policy failed at "Evaluate script execution".
Needs attention
Content-Security-Policy
Issue
script-src allows dangerous script schemes: blob:.
Details
Why it matters
Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.
Check name
Content-Security-Policy
Score
65/100
Status
fail
Category
Security & Trust
Maturity
Established
Goal
Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.
Result
Content-Security-Policy failed at "Evaluate script execution".
Validation steps
Evaluate script execution
script-src allows dangerous script schemes: blob:.
CSP script execution policy is unsafe
Review hardening directives
CSP is missing recommended hardening directives: object-src, base-uri, form-action.
CSP hardening directives are missing or weak
Review CSP reporting
CSP does not define a reporting endpoint.
CSP reporting is missing or incomplete
Evidence log3 steps · 12 lines
Evaluate script execution [fail]! script-src allows dangerous script schemes: blob:.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="script-src" sources=["'self'","'unsafe-inline'","'unsafe-eval'","https://bat.bing.com","https://www.redditstatic.com","https://sc-static.net","https://static.ads-twitter.com","https://connect.facebook.net","https://cdnjs.cloudflare.com","https://js.hs-banner.com","https://js.hsadspixel.net","https://js.usemessages.com","https://www.google-analytics.com","https://www.googletagmanager.com","https://doubleclick.net","https://*.doubleclick.net","https://snap.licdn.com","https://www.youtube-nocookie.com","https://sumo.com","https://*.sumo.com","https://*.livechatinc.com","https://*.hs-scripts.com","https://*.hs-analytics.net","https://go.pardot.com","https://*.cleartax-cdn.com","https://*.clarity.ms","https://*.google.com","https://*.gstatic.com","https://*.sumome.com","https://code.jquery.com","https://*.cloudfront.net","https://*.googleapis.com","https://www.googleadservices.com","https://*.website-files.com","https://*.webflow.io","https://cleartax.mynexthire.com","https://*.factors.ai","https://*.netcoresmartech.com","https://assets.clear.in/cleartax/images/1752568698_lottieplayer.js","https://*.cmp.usercentrics.eu","https://assets.apollo.io","https://assets.clear.in","blob:","https://cleartax.in","https://cdn.jsdelivr.net/npm/","https://*.hsforms.net","https://*.hscollectedforms.net","https://*.hs-banner.com","https://web-sdk.smartlook.com"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":["blob:"]} expected="constrained script sources without unsafe execution allowances" issue="script-src allows dangerous script schemes: blob:."FAILscript-src allows dangerous script schemes: blob:.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri, form-action.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrcFallback=["'self'","'unsafe-inline'","https://clear.navattic.com","https://*.factors.ai","https://*.google.com/","https://www.incometax.gov.in","https://go.arena.im","https://assets1.cleartax-cdn.com","https://www.googletagmanager.com","https://www.redditmedia.com","https://assets.cleartax-cdn.com","https://*.gstatic.com","https://www.google-analytics.com","https://js-agent.newrelic.com","https://api.portal.peppercontent.in","https://cleartax.in","https://*.cleartax.in","https://vc.hotjar.io","https://*.cleartax.co","https://*.cleartax.com","https://cleartax.com","https://www.youtube.com","https://i.tryinteract.com","https://cleartax-media.s3.amazonaws.com","https://*.cloudfront.net","https://web.archive.org","https://img.youtube.com","https://*.googleusercontent.com","https://v.24liveblog.com","https://sentry.io","https://px.ads.linkedin.com","https://doubleclick.net","https://*.doubleclick.net","https://platform.twitter.com","https://cdn.jsdelivr.net","https://browser.sentry-cdn.com/","https://i.ytimg.com","https://code.jquery.com","https://*.googleapis.com","https://www.google.co.in","https://*.clarity.ms","https://sumome.com","https://*.sumome.com","https://clear.in","https://*.clear.in","https://www.w3schools.com","https://cdnjs.cloudflare.com","http://localhost:80","https://*.website-files.com","https://cleartax.mynexthire.com","https://sumo.com","https://*.sumo.com","https://*.livechatinc.com","https://*.hs-scripts.com","https://www.youtube-nocookie.com","https://*.hubapi.com","https://*.hubspot.com","https://*.webflow.io","https://*.s3.ap-south-1.amazonaws.com","https://*.netcoresmartech.com","https://*.cmp.usercentrics.eu","https://assets.apollo.io","https://aplo-evnt.com","https://cdn.embedly.com","https://region1.google-analytics.com","https://www.google-analytics.com","https://www.googleadservices.com","https://bat.bing.com","https://webflow.com/","https://forms-na2.hsforms.com","https://hubspot-forms-static-embed-na2.s3.amazonaws.com"] formCount=1WARNCompare recommended hardening coverage actual=["object-src","base-uri","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri, form-action."WARNCSP is missing recommended hardening directives: object-src, base-uri, form-action.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.
Sign in to see 47 other issues and the full report
Create a free account to unlock every issue, evidence details, exports, and higher free limits.
Fix with MCP or CLI
Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.
Score history
Public scan score over time
Public reports for this website origin. Select any point or report link to open that canonical report.
| Scan date | Score | Readiness | Report |
|---|---|---|---|
| 55/100 | Level 3, Bot-Aware | View report | |
| 48/100 | Level 2, Agent-Limited | Current report |