AdSense Auditor
AdSense Auditor
Approval-first audits
Deep audit reportreadyMar 30, 2026, 12:00 AM

AdSense readiness report

alpyalay.org

A key public URL returned a bot-specific login wall, challenge, redirect loop, or access failure that AdSense review crawlers may not be able to evaluate.. At least one policy-backed blocker remains unresolved in the current audit queue.

Report focus

Optional prior-rejection lens.

All sections visible.

Executive readiness summary

The top layer keeps the decision clear: what was crawled, what blocked review confidence, what signals passed, and how much evidence the report is carrying.

Approval confidence

39/100

blocked with low confidence. At least one policy-backed blocker remains unresolved in the current audit queue.

Pages analyzed

8

15 discovered, 0 rendered, 8 indexed.

Blockers

3

16 total findings, including 5 important and 8 minor items.

Crawler access

blocked

1 key public URL(s) showed bot-specific access blockers or content that reviewers may not be able to evaluate.

Verification

warning

The crawl found partial or missing on-site verification evidence. Search Console verification could still exist, but this audit cannot confirm it.

Navigation risk

2

2 navigation or presentation issue(s) were surfaced across the sampled public pages.

Category scores

The score is decomposed so the fix order is obvious.

Content depth

Measures how substantial the public site looks before rendering.

64/100

Trust signals

Measures whether trust, business identity, and contact signals are easy to find.

68/100

Googlebot visibility

Measures whether Googlebot-style fetches can see enough public value without JS.

10/100

Technical baseline

Measures security headers, speed, navigation stability, and JS-shell risk.

64/100

Policy risk

Measures obvious trust and policy risk surfaced during the crawl.

72/100

Criteria matrix

Crawler access matrix

fail

1 key public URL(s) showed bot-specific access blockers or content that reviewers may not be able to evaluate.

Privacy and disclosure

pass

A privacy policy page was detected and the disclosure language looks plausible.

On-site verification readiness

warning

The crawl found partial or missing on-site verification evidence. Search Console verification could still exist, but this audit cannot confirm it.

Public site footprint

pass

The crawl found 8 public HTML pages and discovered 15 URL(s) overall.

Metadata and indexing hygiene

fail

1 approval-critical page(s) carry noindex; 1 page(s) carry nofollow; 3 page(s) have weak H1s; 1 page(s) are missing a meta description; 1 duplicate title cluster(s) were detected.

Mobile and rendering hygiene

pass

The sampled pages expose mobile viewport and layout basics without obvious reviewer friction.

Link graph and destination integrity

fail

1 broken internal destination(s) beyond primary nav.

Content depth, originality, and site purpose

fail

1 thin public page(s); the homepage still leaves the site's purpose unclear.

Media and accessibility hygiene

warning

2 page(s) lean heavily on weakly optimized media.

Rendered visibility delta

pass

No rendered comparison pages were available.

The approval checklist stays tied to evidence URLs.

Each criterion keeps its status, severity, confidence, summary, and captured evidence URLs visible in the same row.

On-site verification readiness

The crawl found partial or missing on-site verification evidence. Search Console verification could still exist, but this audit cannot confirm it.

warning
Severity
moderate
Confidence
high

Mobile and rendering hygiene

The sampled pages expose mobile viewport and layout basics without obvious reviewer friction.

pass
Severity
minor
Confidence
low
No evidence URLs attached to this check.

Content depth, originality, and site purpose

1 thin public page(s); the homepage still leaves the site's purpose unclear.

fail
Severity
critical
Confidence
medium

Rendered visibility delta

No rendered comparison pages were available.

pass
Severity
moderate
Confidence
low
No evidence URLs attached to this check.

Likely refusal reasons are ranked with source basis and URLs.

This keeps crawler observations, official policy concerns, confidence, and false positives out in the open.

Site behavior: navigation

The public structure may still look confusing or incomplete to a reviewer.

medium

Why this matches: Navigation depth, trust-page discoverability, or low-value archive paths dilute the main site story.

Blocker scope
site
Source basis
mixed
Official concern
Yes

Evidence dossier

Every captured crawler signal has a home.

The left rail pins while each evidence chapter scrolls past, keeping the report narrative stable while the detail changes.

Crawler access

Can the AdSense-facing crawlers reach the important surfaces?

1 key public URL(s) showed bot-specific access blockers or content that reviewers may not be able to evaluate.

critical
Official blockers
1
Key URLs
6

https://alpyalay.org/

homepage page with 3 bot probes.

https://alpyalay.org/
Googlebot Smartphone
ok
Status
200
Words
154
Redirects
0
Robots
Allowed
No probe notes.
Mediapartners-Google
ok
Status
200
Words
154
Redirects
0
Robots
Allowed
No probe notes.
Google-Display-Ads-Bot
ok
Status
200
Words
154
Redirects
0
Robots
Allowed
No probe notes.

https://alpyalay.org/realdex/privacy

legal page with 3 bot probes.

https://alpyalay.org/realdex/privacy
Googlebot Smartphone
ok
Status
200
Words
2,894
Redirects
0
Robots
Allowed
No probe notes.
Mediapartners-Google
ok
Status
200
Words
2,894
Redirects
0
Robots
Allowed
No probe notes.
Google-Display-Ads-Bot
ok
Status
200
Words
2,894
Redirects
0
Robots
Allowed
No probe notes.

https://alpyalay.org/realdex/support

legal page with 3 bot probes.

https://alpyalay.org/realdex/support
Googlebot Smartphone
ok
Status
200
Words
230
Redirects
0
Robots
Allowed
No probe notes.
Mediapartners-Google
ok
Status
200
Words
230
Redirects
0
Robots
Allowed
No probe notes.
Google-Display-Ads-Bot
ok
Status
200
Words
230
Redirects
0
Robots
Allowed
No probe notes.

https://alpyalay.org/realdex/terms

legal page with 3 bot probes.

https://alpyalay.org/realdex/terms
Googlebot Smartphone
ok
Status
200
Words
1,913
Redirects
0
Robots
Allowed
No probe notes.
Mediapartners-Google
ok
Status
200
Words
1,913
Redirects
0
Robots
Allowed
No probe notes.
Google-Display-Ads-Bot
ok
Status
200
Words
1,913
Redirects
0
Robots
Allowed
No probe notes.

https://alpyalay.org/cdn-cgi/l/email-protection

legal page with 3 bot probes.

https://alpyalay.org/cdn-cgi/l/email-protection
Googlebot Smartphone
http error
Status
404
Words
145
Redirects
0
Robots
Allowed
No probe notes.
Mediapartners-Google
http error
Status
404
Words
145
Redirects
0
Robots
Allowed
No probe notes.
Google-Display-Ads-Bot
http error
Status
404
Words
145
Redirects
0
Robots
Allowed
No probe notes.

https://alpyalay.org/realdex/press

about page with 3 bot probes.

https://alpyalay.org/realdex/press
Googlebot Smartphone
ok
Status
200
Words
369
Redirects
0
Robots
Allowed
No probe notes.
Mediapartners-Google
ok
Status
200
Words
369
Redirects
0
Robots
Allowed
No probe notes.
Google-Display-Ads-Bot
ok
Status
200
Words
369
Redirects
0
Robots
Allowed
No probe notes.
No crawler access notes.

Googlebot verdict

Googlebot should see enough public HTML to score the site normally.

The sampled pages expose enough crawl-visible content and links in raw HTML.

good
Status
ready
Allowed by robots
Yes
Blocked by robots
No
Mobile status
200
Raw HTML visibility
good
HTML limit
2,097,152 bytes

Googlebot should see enough public HTML to score the site normally.

The sampled pages expose enough crawl-visible content and links in raw HTML.

Important blocked paths

No important paths were blocked.

Hidden essential content

No essential content hidden URLs were captured.

Late head elements

No late head element URLs were captured.

Stateful content risks

No stateful content risk URLs were captured.
Sitemap discovered
Yes
Meta robots entries
0
None captured
Canonical URLs
0
None captured
HTML byte risk URLs
0
No Googlebot notes.

Robots rules

Robots, sitemaps, crawl delay, and bot-specific allowances.

This section separates ordinary search crawling from the AdSense-relevant crawler rules captured during the audit.

good
Robots URL
https://alpyalay.org/robots.txt
Fetched
Yes
User agent
Googlebot
Root allowed
Yes
Crawl delay
Not captured
Sitemaps
1
https://www.alpyalay.org/sitemap.xml

Important paths blocked

No important blocked paths were captured.

googlebot smartphone

Applicable user-agent: Googlebot

allowed
No important paths blocked for this bot.

mediapartners google

Applicable user-agent: Mediapartners-Google

allowed
No important paths blocked for this bot.

google display ads bot

Applicable user-agent: Google-Display-Ads-Bot

allowed
No important paths blocked for this bot.
No robots notes.

Verification readiness

Ownership and ads.txt signals are kept separate from crawler access.

The crawl found partial or missing on-site verification evidence. Search Console verification could still exist, but this audit cannot confirm it.

moderate
Status
warning
Hint applied
Not captured
Suggested hint
Not captured
Ambiguity
No
Detected methods
3
External note
Search Console ownership is a valid external verification path, but this audit only confirms on-site methods and cannot verify Search Console access.

ads.txt signal

ads.txt is missing at the root URL.

https://alpyalay.org/ads.txt
Reachable
No
Status code
404
Redirects
0
Google entries
0
Publisher IDs
None captured
Valid publisher entry
No
No ads.txt parse issues.

head code

The crawl did not find an AdSense head code signal in the sampled HTML.

missing
Valid placement
No
Publisher ID
Not captured
Source mode
fetch

meta tag

The crawl did not find a google-adsense-account meta tag.

missing
Valid placement
No
Publisher ID
Not captured
Source mode
fetch

Rendering evidence

Raw HTML and rendered snapshots are compared for reviewer-visible gaps.

No rendered comparison pages were available.

good
Framework
nextjs
Rendering mode
next-static-likely
Confidence
high
Pages compared
0
Significant diffs
0
Render capture
Not captured

Why rendering matters

Next.js was detected, but the sampled pages still expose enough raw HTML to look crawler-friendly.

  • next-asset-path

Render diff summary

No rendered comparison pages were available.

Essential content hidden

No hidden essential content found.

Navigation hidden

No hidden navigation URLs found.

Metadata mismatch

No metadata mismatch URLs found.

Content evidence

Content quality, originality, language, and sampled page depth.

The sampled public pages still show thin, duplicate, or non-content patterns that can weaken reviewer confidence.

moderate
Content score
54/100
Content severity
moderate
Originality score
73/100
Originality severity
good
Majority language
en
Supported language majority
Yes

Originality summary

The sampled public pages still show thin, duplicate, or non-content patterns that can weaken reviewer confidence.

Content issues

Thin content across core pages

Increase depth with firsthand examples, FAQs, comparisons, and original insights.

minor

6 pages affected.

Prominent pages lead to too few useful destinations

Strengthen internal linking so key public pages connect into real docs, help, examples, or supporting pages.

moderate

1 page affected.

Placeholder or under-construction pages are still public

Remove unfinished pages from primary navigation or finish them before reapplying.

critical

1 page affected.

Core pages have weak metadata or heading structure

Give each approval-critical page one clear H1, a distinct title, and a useful meta description that explains why the page exists.

moderate

5 pages affected.

Broken internal links weaken content depth

Repair broken internal destinations so supporting pages feel connected and reviewer-visible depth is easier to discover.

moderate

1 page affected.

The site's purpose is still unclear from the public homepage

Clarify who the site is for, what it does, and where a reviewer should go next using stronger hero copy, headings, and supporting internal links.

critical

1 page affected.

Missing pages

About

The site does not clearly explain who is behind the content.

moderate

Thin content pages

https://alpyalay.org/

Only 131 words were found in the fetch-visible content.

homepage
https://alpyalay.org/

Language distribution

  • en: 8 pages (supported)

Duplicate clusters

No duplicate clusters were detected.

Technical health

Headers, HTTPS, and operational fixes from the crawler run.

Technical findings are listed separately from policy and content findings so infrastructure work does not bury editorial work.

moderate
Technical score
53/100
Severity
moderate
Header status
pass
Technical fixes
7

Https

Present in the captured response.

present

Csp

Missing from the captured response.

missing

Hsts

Present in the captured response.

present

X Frame Options

Present in the captured response.

present

X Content Type Options

Present in the captured response.

present

Missing Content-Security-Policy header

The site is missing a CSP header.

minor

Fix: Ship a baseline CSP that covers scripts, styles, and frames safely.

Crawler access matrix surfaced official blockers

1 key public URL(s) showed bot-specific access blockers or content that reviewers may not be able to evaluate.

critical

Fix: Remove crawler-specific login walls, WAF challenges, and unstable redirects from key public URLs.

Cookie-consent signal is weak for a tracked site

Tracking signals were detected, but the public crawl did not see a clear cookie-consent or cookie-settings prompt.

minor
https://alpyalay.org/

Fix: If cookies or analytics require consent in your region, expose a clear cookie banner or settings path and keep the policy disclosures aligned.

Approval-critical pages are marked noindex

One or more public pages that should support approval are explicitly marked noindex.

critical
https://alpyalay.org/cdn-cgi/l/email-protection

Fix: Remove noindex from important public pages that need to look reviewer-visible and durable.

Approval-critical pages are marked nofollow

Some approval-critical pages instruct crawlers not to follow links, which weakens public path discovery.

minor
https://alpyalay.org/cdn-cgi/l/email-protection

Fix: Remove nofollow from important public pages unless the directive is truly intentional.

Public pages lean on heavy or weakly optimized media

Some public pages depend heavily on embedded or weakly optimized media patterns.

minor
https://alpyalay.org/realdex/press

Fix: Lazy-load below-the-fold media, define image dimensions, and reduce reliance on heavyweight embeds on key public pages.

Broken internal links were detected beyond primary navigation

The crawl found broken internal destinations that are still linked from public pages.

moderate
https://alpyalay.org/cdn-cgi/l/email-protection

Fix: Repair or remove broken internal links beyond the main nav so reviewers can move through the site without dead ends.

Policy and trust

Policy violations, trust checklist, and reviewer-facing risk.

This section keeps official policy concerns visible while still showing advisory trust signals.

moderate
Policy score
72/100
Severity
good
Violations
0
Trust checklist
7
No explicit policy violations were flagged.

Googlebot can access core public pages

The sampled pages expose enough crawl-visible content and links in raw HTML.

pass
Source basis
official
Official concern
Yes

Trust pages are present and discoverable

At least one trust page signal is missing or weak in the crawl-visible site.

warning
Source basis
mixed
Official concern
Yes

Homepage exposes reviewer-visible publisher content

The homepage still looks too thin or too UI-heavy for a strong first-pass review.

fail
Source basis
official
Official concern
Yes

Privacy disclosure matches site tracking behavior

Tracking signals exist; make sure the privacy and cookie disclosures are complete.

warning
Source basis
mixed
Official concern
Yes

Cookie-consent path is visible when tracking is present

Tracking signals were detected, but the sampled pages did not show a clear cookie-consent or settings path.

warning
Source basis
mixed
Official concern
No

ads.txt is present (advisory only)

ads.txt was not found. This is usually not what decides application approval, but it is still worth fixing.

warning
Source basis
community
Official concern
No

Domain registration facts are reliable

Domain age came from RDAP registration data.

pass
Source basis
official
Official concern
No

Site profile

Site type, page mix, and domain registration context.

The public footprint is too thin or generic to classify confidently.

info
Site type
unknown
Profile confidence
medium
Registered at
Sep 12, 2022, 01:08 PM
Domain age days
1,294
Domain age years
3.5
Age source
rdap

Site profile rationale

The public footprint is too thin or generic to classify confidently.

homepage

1 page in this crawl sample.

legal

4 pages in this crawl sample.

about

1 page in this crawl sample.

app

2 pages in this crawl sample.

Runtime diagnostics

AI status, source confidence, artifacts, and support diagnostics.

This report is leaning more on observed approval patterns because the deterministic evidence is less policy-specific.

info
AI status
heuristic only
Selected model
Not captured
Fallback model
Not captured
Used fallback
No
Gateway
No
Structured output
No
AI duration
Not captured
Parse failures
0

Source confidence

This report is leaning more on observed approval patterns because the deterministic evidence is less policy-specific.

Official signals
0
Mixed signals
4
Community signals
0
Overall confidence
high

Artifacts

Raw HTML archive
Not captured
Rendered snapshots
0
Rendered artifacts
0
JSON export
Locked
PDF export
Locked
Capture mode
Not captured

Support diagnostics

Publication state
published
Report state
ready
App env
sample
Model profile
premium
Render capture
Not captured
Render attempt
Not captured
  • Frozen public sample generated from a live crawl of alpyalay.org without browser-rendered snapshots.
  • Frozen public sample generated without browser-rendered evidence.
  • Frozen public sample generated without browser-rendered evidence.

Artifact references

No artifact references captured.

Fix queue and remediation plan are printed as a working report.

Findings stay grouped by policy confidence, while the remediation plan gives ordered implementation steps and related URLs.

Official blockers

1

A key public URL returned a bot-specific login wall, challenge, redirect loop, or access failure that AdSense review crawlers may not be able to evaluate.

Make the homepage and trust-critical public URLs reachable without login walls, anti-bot challenges, or unstable redirect chains for Google review crawlers.

critical
https://alpyalay.org/
Detector
crawler_access_matrix
Category
technical
Page type
homepage
Confidence
high
Source basis
official
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: 1 key public URL(s) showed bot-specific access blockers or content that reviewers may not be able to evaluate.

Fetch snippet: ((a,b,c,d,e,f,g,h)=>{let i=document.documentElement,j=["light","dark"];function k(b){var c;(Array.isArray(a)?a:[a]).forEach(a=>{let c="class"===a,d=c&&f?e.map(a=>f[a]||a):e;c?(i.classList.remove(...d),i.classList.add(f&&f[b]?f[b]:b)):i.setAttribute(a,b)}),c=b,h&&j.includes(c)&&(i.style.colorScheme=c)}if(d)k(d);else try{let a=localStorage.getItem(b)||c,d=g&&"system"===a?window.matchMedia("(prefers-color-scheme: dark)…

Inferred risks

9

Thin public pages make the site look like a shallow marketing shell rather than a substantive property worth monetizing.

Expand the page with concrete use cases, screenshots, examples, FAQs, and proof that the page serves a distinct visitor need.

critical
https://alpyalay.org/
Detector
thin_public_page
Category
content-depth
Page type
homepage
Confidence
high
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: Fetched HTML exposed only 131 words on this page.

Metric: 131 fetched words

Fetch snippet: ((a,b,c,d,e,f,g,h)=>{let i=document.documentElement,j=["light","dark"];function k(b){var c;(Array.isArray(a)?a:[a]).forEach(a=>{let c="class"===a,d=c&&f?e.map(a=>f[a]||a):e;c?(i.classList.remove(...d),i.classList.add(f&&f[b]?f[b]:b)):i.setAttribute(a,b)}),c=b,h&&j.includes(c)&&(i.style.colorScheme=c)}if(d)k(d);else try{let a=localStorage.getItem(b)||c,d=g&&"system"===a?window.matchMedia("(prefers-color-scheme: dark)…

The homepage still does not make the site's purpose, audience, or next step obvious enough on first inspection.

Clarify the homepage heading, supporting copy, and internal paths so a cold reviewer can understand the site's purpose immediately.

critical
https://alpyalay.org/
Detector
site_purpose_unclear
Category
content-depth
Page type
homepage
Confidence
medium
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: The homepage combines low visible copy, weak purpose signals, and too few supporting internal paths.

Fetch snippet: ((a,b,c,d,e,f,g,h)=>{let i=document.documentElement,j=["light","dark"];function k(b){var c;(Array.isArray(a)?a:[a]).forEach(a=>{let c="class"===a,d=c&&f?e.map(a=>f[a]||a):e;c?(i.classList.remove(...d),i.classList.add(f&&f[b]?f[b]:b)):i.setAttribute(a,b)}),c=b,h&&j.includes(c)&&(i.style.colorScheme=c)}if(d)k(d);else try{let a=localStorage.getItem(b)||c,d=g&&"system"===a?window.matchMedia("(prefers-color-scheme: dark)…

A prominent public page leads to too few additional destinations, which makes the site feel like a dead-end shell.

Add stronger internal paths, examples, docs, or related content so important pages connect users deeper into the site.

moderate
https://alpyalay.org/
Detector
dead_end_prominent_page
Category
site-structure
Page type
homepage
Confidence
medium
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: This prominent public page exposes very few internal paths, which makes the site feel like a dead end.

The public site does not clearly explain who is behind the content or business.

Publish an about page with publisher identity, purpose, and why the public content exists.

moderate
https://alpyalay.org/
Detector
about_page_missing
Category
trust
Page type
homepage
Confidence
high
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: No about-page signal was detected in the public crawl.

Fetch snippet: ((a,b,c,d,e,f,g,h)=>{let i=document.documentElement,j=["light","dark"];function k(b){var c;(Array.isArray(a)?a:[a]).forEach(a=>{let c="class"===a,d=c&&f?e.map(a=>f[a]||a):e;c?(i.classList.remove(...d),i.classList.add(f&&f[b]?f[b]:b)):i.setAttribute(a,b)}),c=b,h&&j.includes(c)&&(i.style.colorScheme=c)}if(d)k(d);else try{let a=localStorage.getItem(b)||c,d=g&&"system"===a?window.matchMedia("(prefers-color-scheme: dark)…

This public page is explicitly marked noindex even though it appears to be part of the approval-facing site footprint.

Remove noindex from approval-critical pages that should remain visible and reviewable in public search-oriented crawls.

moderate
https://alpyalay.org/cdn-cgi/l/email-protection
Detector
noindex_approval_page
Category
technical
Page type
legal
Confidence
high
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: Meta robots directives on this page include: noindex, nofollow.

Fetch snippet: Please enable cookies. You are unable to access this email address alpyalay.org The website from which you got to this page is protected by Cloudflare. Email addresses on that page have been hidden in order to keep them from being accessed by malicious bots. You must enable Javascript in your browser in order to decode the e-mail address. If you have a website and are interested in protecting it in a similar way, yo…

A linked internal page returned an error from within the sampled site graph, which weakens reviewer confidence in site completeness.

Repair or remove the broken internal destination and update any pages that still link to it.

moderate
https://alpyalay.org/cdn-cgi/l/email-protection
Detector
broken_internal_link
Category
site-structure
Page type
legal
Confidence
high
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: Linked from 4 sampled page(s), but returned 404.

Fetch snippet: Please enable cookies. You are unable to access this email address alpyalay.org The website from which you got to this page is protected by Cloudflare. Email addresses on that page have been hidden in order to keep them from being accessed by malicious bots. You must enable Javascript in your browser in order to decode the e-mail address. If you have a website and are interested in protecting it in a similar way, yo…

Several approval-facing pages share the same title pattern, which makes the site feel templated and less deliberate.

Give each important public page a distinct title that matches its specific content and destination intent.

moderate
https://alpyalay.org/realdex/support
Detector
duplicate_title_cluster
Category
content-depth
Page type
legal
Confidence
high
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: Duplicate title cluster: "RealDex - Catch Real Animals, Build Your Dex | Alp Yalay" across 2 URL(s).

The site is missing a CSP header.

Ship a baseline CSP that covers scripts, styles, and frames safely.

minor
https://alpyalay.org/
Detector
technical_missing_content_security_policy_header
Category
technical
Page type
homepage
Confidence
high
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: Missing Content-Security-Policy header

Fetch snippet: ((a,b,c,d,e,f,g,h)=>{let i=document.documentElement,j=["light","dark"];function k(b){var c;(Array.isArray(a)?a:[a]).forEach(a=>{let c="class"===a,d=c&&f?e.map(a=>f[a]||a):e;c?(i.classList.remove(...d),i.classList.add(f&&f[b]?f[b]:b)):i.setAttribute(a,b)}),c=b,h&&j.includes(c)&&(i.style.colorScheme=c)}if(d)k(d);else try{let a=localStorage.getItem(b)||c,d=g&&"system"===a?window.matchMedia("(prefers-color-scheme: dark)…

Tracking signals were detected, but the public crawl did not see a clear cookie-consent or cookie-settings prompt.

If cookies or analytics require consent in your region, expose a clear cookie banner or settings path and keep the policy disclosures aligned.

minor
https://alpyalay.org/
Detector
technical_cookie_consent_signal_is_weak_for_a_tracked_site
Category
technical
Page type
homepage
Confidence
low
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: Cookie-consent signal is weak for a tracked site

Fetch snippet: ((a,b,c,d,e,f,g,h)=>{let i=document.documentElement,j=["light","dark"];function k(b){var c;(Array.isArray(a)?a:[a]).forEach(a=>{let c="class"===a,d=c&&f?e.map(a=>f[a]||a):e;c?(i.classList.remove(...d),i.classList.add(f&&f[b]?f[b]:b)):i.setAttribute(a,b)}),c=b,h&&j.includes(c)&&(i.style.colorScheme=c)}if(d)k(d);else try{let a=localStorage.getItem(b)||c,d=g&&"system"===a?window.matchMedia("(prefers-color-scheme: dark)…

Advisories

6

The main heading is so short that it does not clearly explain the page's distinct role.

Rewrite the H1 so it states the page topic, audience, or concrete promise more explicitly.

minor
https://alpyalay.org/
Detector
weak_h1
Category
content-depth
Page type
homepage
Confidence
medium
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: Current H1: "Alp Yalay".

Fetch snippet: ((a,b,c,d,e,f,g,h)=>{let i=document.documentElement,j=["light","dark"];function k(b){var c;(Array.isArray(a)?a:[a]).forEach(a=>{let c="class"===a,d=c&&f?e.map(a=>f[a]||a):e;c?(i.classList.remove(...d),i.classList.add(f&&f[b]?f[b]:b)):i.setAttribute(a,b)}),c=b,h&&j.includes(c)&&(i.style.colorScheme=c)}if(d)k(d);else try{let a=localStorage.getItem(b)||c,d=g&&"system"===a?window.matchMedia("(prefers-color-scheme: dark)…

This public page uses a nofollow directive, which can weaken how confidently crawlers traverse important supporting links.

Remove nofollow from approval-facing pages unless it is a deliberate and necessary indexing decision.

minor
https://alpyalay.org/cdn-cgi/l/email-protection
Detector
nofollow_approval_page
Category
technical
Page type
legal
Confidence
high
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: Meta robots directives on this page include: noindex, nofollow.

Fetch snippet: Please enable cookies. You are unable to access this email address alpyalay.org The website from which you got to this page is protected by Cloudflare. Email addresses on that page have been hidden in order to keep them from being accessed by malicious bots. You must enable Javascript in your browser in order to decode the e-mail address. If you have a website and are interested in protecting it in a similar way, yo…

A missing meta description makes the page look less curated and less clearly differentiated in the crawl sample.

Add a concise meta description that summarizes the page's purpose and value in plain language.

minor
https://alpyalay.org/cdn-cgi/l/email-protection
Detector
missing_meta_description
Category
content-depth
Page type
legal
Confidence
high
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: No meta description was detected on this page.

Fetch snippet: Please enable cookies. You are unable to access this email address alpyalay.org The website from which you got to this page is protected by Cloudflare. Email addresses on that page have been hidden in order to keep them from being accessed by malicious bots. You must enable Javascript in your browser in order to decode the e-mail address. If you have a website and are interested in protecting it in a similar way, yo…

This page leans heavily on embedded or weakly optimized media patterns, which can make the first public impression feel heavy or unstable.

Optimize media, define dimensions, lazy-load lower-priority assets, and reduce unnecessary embeds on this page.

minor
https://alpyalay.org/realdex
Detector
heavy_media_proxy
Category
technical
Page type
app
Confidence
medium
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: 23 heavy-media signal(s) were detected on this page.

Metric: 23 heavy-media signal(s)

Fetch snippet: RealDexComing Summer 2026AI-Powered Wildlife CollectionPhotograph real animals. Build your real-world Dex.AI identifies 10,000+ species — right from your camera.Coming Summer 2026How RealDex WorksThree steps to start your wildlife collection1Scan WildlifeOpen your camera and point at any animal. Our on-device AI detects creatures in real-time at 30fps.2Get an AI MatchThe AI identifies the species instantly from 10,0…

The main heading is so short that it does not clearly explain the page's distinct role.

Rewrite the H1 so it states the page topic, audience, or concrete promise more explicitly.

minor
https://alpyalay.org/realdex/press
Detector
weak_h1
Category
content-depth
Page type
about
Confidence
medium
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: Current H1: "Press Kit".

Fetch snippet: RealDex is an AI-powered wildlife collection app that turns every walk into a wildlife expedition. Users photograph real animals and build a real-world Pokédex. The app uses a dual on-device AI pipeline — YOLO26n ("The Finder") detects animals at 30fps and BioCLIP Int8 ("The Professor") identifies over 10,000 species — all running entirely on the user's device with no internet required.For uncertain identifications,…

This page leans heavily on embedded or weakly optimized media patterns, which can make the first public impression feel heavy or unstable.

Optimize media, define dimensions, lazy-load lower-priority assets, and reduce unnecessary embeds on this page.

minor
https://alpyalay.org/realdex/press
Detector
heavy_media_proxy
Category
technical
Page type
about
Confidence
medium
Source basis
mixed
Evidence mode
fetch
Source mode
fetch
Status
new

Evidence: 15 heavy-media signal(s) were detected on this page.

Metric: 15 heavy-media signal(s)

Fetch snippet: RealDex is an AI-powered wildlife collection app that turns every walk into a wildlife expedition. Users photograph real animals and build a real-world Pokédex. The app uses a dual on-device AI pipeline — YOLO26n ("The Finder") detects animals at 30fps and BioCLIP Int8 ("The Professor") identifies over 10,000 species — all running entirely on the user's device with no internet required.For uncertain identifications,…

The action plan moves from global blockers to page-level work.

Priority steps, reapply criteria, and page fix briefs are kept together so the user can actually work the report.

Reapply recommendation

Do not reapply yet.

blocked

Critical crawl, policy, or trust blockers are still present. Reapplying now is likely to waste a review cycle.

Recommended wait
14 days
Blockers remaining
7
  • Public site is crawlable without hard blockers: needs-work. At least one policy-backed blocker remains unresolved in the current audit queue.
  • Core trust pages are visible in raw HTML: ready. Privacy and contact signals were detected.
  • Official blockers are cleared: needs-work. 1 official blocker(s) remain in the current fix queue.

1. A key public URL returned a bot-specific login wall, challenge, redirect loop, or access failure that AdSense review crawlers may not be able to evaluate.

Make the homepage and trust-critical public URLs reachable without login walls, anti-bot challenges, or unstable redirect chains for Google review crawlers.

high
Blocker scope
page
Source basis
mixed
Official concern
Yes
Related reasons
low_value_content, thin_content, insufficient_content, site_behavior_navigation

2. Thin public pages make the site look like a shallow marketing shell rather than a substantive property worth monetizing.

Expand the page with concrete use cases, screenshots, examples, FAQs, and proof that the page serves a distinct visitor need.

high
Blocker scope
page
Source basis
mixed
Official concern
Yes
Related reasons
low_value_content, thin_content, insufficient_content, site_behavior_navigation

3. The homepage still does not make the site's purpose, audience, or next step obvious enough on first inspection.

Clarify the homepage heading, supporting copy, and internal paths so a cold reviewer can understand the site's purpose immediately.

high
Blocker scope
page
Source basis
mixed
Official concern
Yes
Related reasons
low_value_content, thin_content, insufficient_content, site_behavior_navigation

4. A prominent public page leads to too few additional destinations, which makes the site feel like a dead-end shell.

Add stronger internal paths, examples, docs, or related content so important pages connect users deeper into the site.

medium
Blocker scope
site
Source basis
mixed
Official concern
Yes
Related reasons
low_value_content, thin_content, insufficient_content, site_behavior_navigation

5. The public site does not clearly explain who is behind the content or business.

Publish an about page with publisher identity, purpose, and why the public content exists.

medium
Blocker scope
site
Source basis
mixed
Official concern
Yes
Related reasons
low_value_content, thin_content, insufficient_content, site_behavior_navigation

Page briefs turn crawl findings into implementation notes.

Each page keeps its focus, missing elements, rewrite goals, implementation checklist, avoid patterns, evidence, and related reason IDs.

Publisher-content depth

Make the homepage and trust-critical public URLs reachable without login walls, anti-bot challenges, or unstable redirect chains for Google review crawlers.

Priority 1
https://alpyalay.org/
Page type
homepage
Source basis
mixed
Related reasons
low_value_content, thin_content, insufficient_content, site_behavior_navigation

Missing elements

  • Examples
  • FAQs
  • Original detail

Rewrite goals

  • Explain the page purpose in reviewer-friendly terms.
  • Show concrete value without relying on interaction or hidden state.
  • Add domain-specific trust and support context where relevant.

Implementation checklist

  • State who the page is for and what problem it solves near the top.
  • Add concrete examples, screenshots, comparisons, or outcomes.
  • Include reviewer-visible context, not just generic marketing copy.
  • Remove or noindex thin sibling pages if they dilute this section.

Avoid patterns

  • Do not pad the page with generic filler just to raise word count.
  • Do not leave the page as a thin marketing shell without proof, examples, or depth.
  • 1 key public URL(s) showed bot-specific access blockers or content that reviewers may not be able to evaluate.

Publisher-content depth

Expand the page with concrete use cases, screenshots, examples, FAQs, and proof that the page serves a distinct visitor need.

Priority 2
https://alpyalay.org/
Page type
homepage
Source basis
mixed
Related reasons
low_value_content, thin_content, insufficient_content, site_behavior_navigation

Missing elements

  • Examples
  • FAQs
  • Original detail

Rewrite goals

  • Explain the page purpose in reviewer-friendly terms.
  • Show concrete value without relying on interaction or hidden state.
  • Add domain-specific trust and support context where relevant.

Implementation checklist

  • State who the page is for and what problem it solves near the top.
  • Add concrete examples, screenshots, comparisons, or outcomes.
  • Include reviewer-visible context, not just generic marketing copy.
  • Remove or noindex thin sibling pages if they dilute this section.

Avoid patterns

  • Do not pad the page with generic filler just to raise word count.
  • Do not leave the page as a thin marketing shell without proof, examples, or depth.
  • Fetched HTML exposed only 131 words on this page.
  • 131 fetched words

Publisher-content depth

Clarify the homepage heading, supporting copy, and internal paths so a cold reviewer can understand the site's purpose immediately.

Priority 3
https://alpyalay.org/
Page type
homepage
Source basis
mixed
Related reasons
low_value_content, thin_content, insufficient_content, site_behavior_navigation

Missing elements

  • Examples
  • FAQs
  • Original detail

Rewrite goals

  • Explain the page purpose in reviewer-friendly terms.
  • Show concrete value without relying on interaction or hidden state.
  • Add domain-specific trust and support context where relevant.

Implementation checklist

  • State who the page is for and what problem it solves near the top.
  • Add concrete examples, screenshots, comparisons, or outcomes.
  • Include reviewer-visible context, not just generic marketing copy.
  • Remove or noindex thin sibling pages if they dilute this section.

Avoid patterns

  • Do not pad the page with generic filler just to raise word count.
  • Do not leave the page as a thin marketing shell without proof, examples, or depth.
  • The homepage combines low visible copy, weak purpose signals, and too few supporting internal paths.

Publisher-content depth

Add stronger internal paths, examples, docs, or related content so important pages connect users deeper into the site.

Priority 4
https://alpyalay.org/
Page type
homepage
Source basis
mixed
Related reasons
low_value_content, thin_content, insufficient_content, site_behavior_navigation

Missing elements

  • Examples
  • FAQs
  • Original detail

Rewrite goals

  • Explain the page purpose in reviewer-friendly terms.
  • Show concrete value without relying on interaction or hidden state.
  • Add domain-specific trust and support context where relevant.

Implementation checklist

  • State who the page is for and what problem it solves near the top.
  • Add concrete examples, screenshots, comparisons, or outcomes.
  • Include reviewer-visible context, not just generic marketing copy.
  • Remove or noindex thin sibling pages if they dilute this section.

Avoid patterns

  • Do not pad the page with generic filler just to raise word count.
  • Do not leave the page as a thin marketing shell without proof, examples, or depth.
  • This prominent public page exposes very few internal paths, which makes the site feel like a dead end.

Trust and reviewer clarity

Publish an about page with publisher identity, purpose, and why the public content exists.

Priority 5
https://alpyalay.org/
Page type
homepage
Source basis
mixed
Related reasons
low_value_content, thin_content, insufficient_content, site_behavior_navigation

Missing elements

  • Owner identity
  • Contact path
  • Policy clarity

Rewrite goals

  • Explain the page purpose in reviewer-friendly terms.
  • Show concrete value without relying on interaction or hidden state.
  • Add domain-specific trust and support context where relevant.

Implementation checklist

  • Show a real owner, brand, or editorial identity on the page.
  • Add a visible path to Contact, Privacy, and Terms without relying on hidden menus.
  • Make policy text domain-specific and aligned with actual tracking or cookie behavior.
  • Remove or noindex thin sibling pages if they dilute this section.

Avoid patterns

  • Do not use copied policy templates that still mention another brand or placeholder token.
  • Do not hide trust links only in account menus, drawers, or post-login areas.
  • No about-page signal was detected in the public crawl.

Publisher-content depth

Remove noindex from approval-critical pages that should remain visible and reviewable in public search-oriented crawls.

Priority 6
https://alpyalay.org/cdn-cgi/l/email-protection
Page type
legal
Source basis
mixed
Related reasons
low_value_content, thin_content, site_behavior_navigation

Missing elements

  • Examples
  • FAQs
  • Original detail

Rewrite goals

  • Explain the page purpose in reviewer-friendly terms.
  • Show concrete value without relying on interaction or hidden state.
  • Add domain-specific trust and support context where relevant.

Implementation checklist

  • State who the page is for and what problem it solves near the top.
  • Add concrete examples, screenshots, comparisons, or outcomes.
  • Include reviewer-visible context, not just generic marketing copy.
  • Remove or noindex thin sibling pages if they dilute this section.

Avoid patterns

  • Do not pad the page with generic filler just to raise word count.
  • Do not leave the page as a thin marketing shell without proof, examples, or depth.
  • Meta robots directives on this page include: noindex, nofollow.

Reason playbooks preserve the research layer behind each fix.

Reported fix patterns, failure patterns, official anchors, and source labels remain available inside the report instead of being hidden in exports.

Low value content

The site is public and crawlable, but it does not yet show enough original, reviewer-visible value across its key pages.

high
Evidence confidence
high
Source basis
mixed
Community frequency
Largest cluster in the reviewed historical refusal cases.

Common evidence patterns

  • Core pages stay thin even when the site has multiple URLs.
  • Trust pages are weak or absent.
  • The site purpose is hard to infer from the homepage and top pages.

Recommended fixes

  • Strengthen About, Contact, privacy, and terms pages.
  • Add firsthand examples, comparisons, screenshots, and FAQs to weak pages.
  • Reduce mixed-purpose or low-value sections that dilute the site story.

False positives and small details

  • False positive: Strong articles can still be rejected when legal and identity pages are weak.
  • False positive: Good traffic alone does not offset thin crawl-visible content.
  • Check: Footer links should expose About, Contact, Privacy, and Terms on mobile too.
  • Check: Privacy disclosures should match actual analytics, cookies, and tracking behavior.
  • Check: Empty categories and search-style pages should not dominate the visible crawl path.

Reported outcomes and source anchors

  • Fix pattern: Pruning thin tag and category pages.
  • Fix pattern: Improving trust pages and author identity.
  • Fix pattern: Fixing mobile readability and broken legal pages.
  • Failure pattern: Adding more generic articles without improving trust, originality, or site clarity.
  • Failure pattern: Reapplying after cosmetic changes while the public footprint still looks mixed or thin.
  • Failure pattern: Padding weak pages with filler copy instead of adding firsthand detail.
  • Official anchor: Google Search helpful, reliable, people-first content guidance
  • Official anchor: Google Publisher Policies
  • Source: Historical refusal cases
  • Source: Publisher support case synthesis
  • Source: Official Google guidance

Thin content

Several public pages exist, but too many of them have low information gain or function mostly as lists, stubs, or shells.

high
Evidence confidence
high
Source basis
mixed
Community frequency
Common overlap bucket inside 'low value' discussions; repeatedly linked to tags, categories, and templated pages.

Common evidence patterns

  • Weak average word count across key pages.
  • Archive, tag, or category pages dominate the crawl footprint.
  • Important pages add little beyond templated marketing copy.

Recommended fixes

  • Prune or noindex thin taxonomy and archive pages.
  • Expand weak pages with original analysis and reviewer-facing detail.
  • Replace repetitive templates with fewer, stronger public pages.

False positives and small details

  • False positive: Short pages can still pass when they serve a narrow purpose and link to deeper content.
  • Check: Tag, author, and archive pages should either add real value or stay out of indexable paths.
  • Check: Titles and intros should clearly differentiate similar pages.
  • Check: Reviewer-facing pages should include examples, screenshots, or comparisons where useful.

Reported outcomes and source anchors

  • Fix pattern: Noindexing empty taxonomies and archives.
  • Fix pattern: Consolidating repetitive pages into stronger cornerstones.
  • Fix pattern: Adding screenshots, comparisons, and original insight.
  • Failure pattern: Keeping thin tag, author, and archive pages indexed after expanding only the main posts.
  • Failure pattern: Mass-producing similar pages with different headings but little new information gain.
  • Failure pattern: Treating word count alone as the fix while the page still reads like a stub or list.
  • Official anchor: Google Search helpful content guidance
  • Official anchor: Google Publisher Policies
  • Source: Thin-content case patterns
  • Source: Publisher support case synthesis
  • Source: Official Google guidance

Insufficient content

The public site footprint is too small for a reviewer or crawler to understand the site clearly.

high
Evidence confidence
high
Source basis
mixed
Community frequency
Regularly reported on smaller sites and tool-style properties, especially when the crawlable footprint stayed below reviewable depth.

Common evidence patterns

  • Very few crawlable public pages.
  • Homepage and support pages do not establish enough scope or depth.
  • Tool-like sites rely on interface value without editorial context.

Recommended fixes

  • Publish more crawlable public pages before reapplying.
  • Add docs, tutorials, examples, or support pages around the core offer.
  • Ensure the homepage explains the site clearly without requiring interaction.

False positives and small details

  • False positive: A small site can still pass if the few pages are unusually strong and complete.
  • Check: The homepage should explain the site before any signup, search, or interaction.
  • Check: A few strong anchor pages are more persuasive than many near-empty ones.
  • Check: Request indexing only after the new pages are live and internally linked.

Reported outcomes and source anchors

  • Fix pattern: Adding public docs and support content for tools.
  • Fix pattern: Expanding the homepage into a reviewer-readable overview.
  • Fix pattern: Waiting for indexing after publishing stronger anchor pages.
  • Failure pattern: Reapplying before enough strong anchor pages are public and crawlable.
  • Failure pattern: Leaving the homepage dependent on interaction while docs or support pages remain absent.
  • Failure pattern: Assuming a small page count is fine when the few pages still look incomplete.
  • Official anchor: Google Publisher Policies
  • Official anchor: Google Search technical requirements
  • Source: Insufficient-content case patterns
  • Source: Publisher support case synthesis
  • Source: Official Google guidance

Site behavior: navigation

The site structure or navigation likely feels confusing, incomplete, or misleading to a reviewer.

medium
Evidence confidence
medium
Source basis
mixed
Community frequency
Less frequent than low-value content, but very distinctive when users reported misleading menus, broken links, or unfinished navigation.

Common evidence patterns

  • Important public trust pages are missing.
  • Low-value navigation and archive pages crowd the crawl footprint.
  • The site purpose and route hierarchy are unclear.

Recommended fixes

  • Simplify navigation around a clear public site story.
  • Make About, Contact, privacy, and terms links easy to find.
  • Remove dead-end and low-value archive pages from prominent crawl paths.

False positives and small details

  • False positive: A small navigation can be fine if core trust and content pages are obvious.
  • Check: Broken or placeholder trust-page routes on mobile can sink an otherwise decent review.
  • Check: Main menus should not promote empty sections, thin archives, or dead-end pages.
  • Check: Cookie banners, popups, and sliders should not obscure core navigation or content.

Reported outcomes and source anchors

  • Fix pattern: Cleaning menus and removing empty categories.
  • Fix pattern: Fixing broken trust-page routes and misleading UI elements.
  • Fix pattern: Improving mobile navigation and theme quality.
  • Failure pattern: Keeping empty categories, dead-end pages, or confusing menu labels in the main crawl path.
  • Failure pattern: Fixing content while leaving trust pages buried or broken on mobile.
  • Failure pattern: Using aggressive popups, sliders, or under-construction UI that weakens review confidence.
  • Official anchor: Google policy help on misleading navigation
  • Official anchor: Google inventory value policy
  • Source: Site-structure case patterns
  • Source: Official policy help references

Advisory signals stay visible without mixing them into blockers.

These are useful context for reviewer trust, but the report keeps source basis and official policy flags clear.

No advisory signals captured.

Appendix

Crawler evidence map.

The main report interprets the data. The appendix keeps the crawl shape readable while worker-backed exports carry the full machine-readable report for eligible audits.

Crawl scope

Discovered
15
Analyzed
8
Indexed
8
Rendered
0

Access and exports

Report access
Open
Export access
Locked
Retention
active
Hidden premium items
0

Selected page types

homepage

1 page represented

legal

4 pages represented

about

1 page represented

app

2 pages represented

Locked premium detail

Findings
0
Refusal reasons
0
Playbooks
0
Remediation steps
0
Page briefs
0
Checklists
0