Broken sitemap discovery
What was verified: robots.txt points to https://buttoneyes.in/sitemap_index.xml, which returns 404.
Business impact: Crawl discovery weakens, new pages surface more slowly, and confidence in site structure drops.
Prepared by
with
Prepared for
Technical precision. Revenue growth. White-hat SEO.
Growth Retainer Proposal
Button Eyes Resort SEO Audit, Recovery Roadmap, and Growth Proposal
A validated audit report and 90-day growth proposal built from the shared source files, corrected with live verification, and structured to turn this audit into a measurable SEO recovery and booking-growth engagement.
Prepared by SEO With Faiz
Prepared for Button Eyes Resort
Date: 25 May 2026
Status: Audit stage
Engagement options included
Critical blockers
4
Discovery, duplicate content, content quality, conversion UX
Validated corrections
4
OG, schema, alt text, and H1 assumptions corrected
Immediate horizon
90 days
Cleanup first, growth second
Data maturity
Early
GA4 and GSC setup is too recent for a mature baseline
Executive Summary
Search visibility is being limited by weak inputs, not by a lack of opportunity.
Button Eyes Resort already has a live site with indexable core pages. The bigger problem is that search engines and users are being asked to trust a site that still contains duplicate blog URLs, weak commercial page targeting, placeholder content, a broken sitemap reference, and visible template leftovers.
Why a retainer is the right model
- The problems are interconnected across crawl health, content quality, metadata, and booking UX.
- Search Console and GA4 baselines are still maturing, so follow-through matters more than a one-time handoff.
- Several recommendations need rechecking after implementation, which is where static audits lose value.
- The best chance of visible progress comes from cleanup plus continued execution, not diagnosis alone.
What happens in the first 30 days
- Sitemap and indexation cleanup is prioritized first.
- Duplicate blog and low-value URL decisions are locked down.
- FAQ, experiences, and core commercial pages get rewrite direction.
- Measurement baselines are cleaned up so future gains can be tracked credibly.
What was reviewed
-
Open full shared audit folder
Master source folder containing the audit documents, crawl exports, and notes.
-
BUTTONEYES RESORT AUDIT SHEET
Primary issue inventory used as the base audit sheet.
-
Button Eyes - Indexing Issues
Indexed URL list and response-code checks.
-
Button Eyes Resort - URL Indexing
URL inventory including duplicate and low-value blog URLs.
-
Screaming Frog Crawl Data - Raw
Raw crawl output covering titles, canonicals, headings, media, and technical signals.
-
GA4 And GSC Data
Analytics and Search Console setup notes, with limitations because setup is recent.
-
Button Eyes resort Keyword list
Commercial and local-intent keyword targets for Hyderabad resort queries.
How gaps were filled
- Live checks across 11 core URLs
- Validation of 6 blog URLs and 2 category URLs
- Verification of
robots.txtand sitemap behavior - Manual checks of page structure, metadata, schema, and visible UX issues
Priority Findings
Highest-risk issues that need immediate attention
Duplicate blog URLs remain indexable
What was verified: Duplicate post pairs are live, indexable, and self-canonicalized instead of consolidating to a preferred version.
Business impact: Relevance splits, crawl budget is wasted, and low-value pages occupy index space that should support commercial intent.
Placeholder and irrelevant content
What was verified: The FAQ page contains Lorem Ipsum, the experiences page contains placeholder amenity copy, and the blog contains irrelevant template travel posts.
Business impact: Trust drops, local topical relevance weakens, and ranking potential for Hyderabad resort intent stays capped.
Broken booking and search UX
What was verified: A booking shortcode is visibly rendering on public pages instead of a working booking or search interface.
Business impact: Conversion confidence drops, pages look unfinished, and booking-intent traffic faces avoidable friction.
Weak commercial page structure
What was verified: The homepage and bookings page are missing an H1, /experinces/ is misspelled, and metadata is often generic or error-prone.
Business impact: Click-through, intent alignment, and quality signals all stay weaker than they should be.
Mobile performance remains weak
What was verified: Source audit reports mobile 34, desktop 65, FCP 3.1s, LCP 8.2s, and CLS 0.01. Crawl data also supports a heavy media and plugin footprint.
Business impact: Rankings, engagement, and booking-intent conversion can all underperform on mobile.
Corrections
Source-audit claims that required correction after validation
Open Graph and social metadata
The source audit marked these as missing. Sampled live pages did contain og:title, og:description, and og:image.
The real issue is quality and consistency, not total absence.
Structured data
The source audit marked schema as missing. Sampled live pages contained JSON-LD for organization, website, webpage, and article-level content.
Schema exists, but it does not offset content quality and duplicate indexation issues.
Alt text assumptions
The source audit suggested blanket image alt failures. Sampled core pages had image alt attributes present.
Media weight, image strategy, and overall content quality are the more pressing concerns.
Heading structure
The source audit implied all pages were missing H1s. That is not accurate.
The most important H1 gaps are the homepage and bookings page, not the entire site.
Important limitation
Google Search Console page indexing is still processing, and GA4 / GSC were only recently set up. That means coverage and traffic baselines are not mature enough yet to support a detailed performance story. The strongest present-tense value here is the cleanup roadmap, not a mature results dashboard.
Roadmap
Recommended 90-day recovery path
| Phase | Timeline | Primary work |
|---|---|---|
| Phase 1: Technical stabilization | Week 1 to Week 2 | Fix sitemap generation, resubmit in Search Console, decide duplicate URL handling, remove visible shortcode output, and correct structural issues on core templates. |
| Phase 2: Content and on-page cleanup | Week 2 to Week 5 | Rewrite homepage, FAQ, experiences, and bookings direction; remove or replace irrelevant blog content; improve metadata and intent mapping for core commercial pages. |
| Phase 3: Local growth foundation | Week 5 to Week 12 | Map target keywords, improve local entity signals, strengthen internal linking, set reporting definitions, and re-audit implemented changes. |
Immediate KPI targets
- Valid live sitemap submitted and crawled
- Duplicate blog URLs removed or consolidated
- Placeholder content removed from FAQ and experiences pages
- Homepage and bookings page fixed structurally
Short-term SEO targets
- Unique titles, meta descriptions, and H1s on key commercial pages
- Cleaner index profile in Search Console
- Better topical fit for Hyderabad resort intent
- Improved landing-page trust and conversion readiness
Business risk if cleanup is skipped
- Traffic work compounds slowly or not at all
- Search engines keep surfacing low-value URLs
- Users hit broken or unconvincing experiences
- SEO spend gets diluted by avoidable technical debt
What success should look like by day 90
A cleaner index profile, stronger commercial pages, improved local relevance, and a much more reliable foundation for organic bookings and enquiry growth. The goal of this phase is not vanity reporting. It is to make the website genuinely ready for sustained SEO work that can be scaled with confidence.
Evidence Appendix
Data sources and claim-level references
Primary data links
-
Shared Google Drive folder
Master folder for all supplied audit assets.
-
Audit sheet
Primary issue list, performance notes, and action comments.
-
Screaming Frog crawl data
Technical crawl export covering URLs, headings, metadata, and assets.
-
GA4 and GSC notes
Setup-stage analytics notes and source limitations.
Live verification links
-
robots.txt
Shows the sitemap path currently referenced by the site.
-
Broken sitemap endpoint
Returns 404, which is central to the discovery issue.
-
Blog index
Shows duplicate and irrelevant blog content in a live context.
-
FAQ page
Shows placeholder FAQ content.
-
Experiences page
Shows the misspelled URL slug and placeholder amenity descriptions.
| Claim in this report | Drive source | Live check |
|---|---|---|
| The sitemap/discovery layer is broken. | Audit sheet | robots.txt and sitemap endpoint |
| Duplicate blog URLs remain live and indexable. | URL indexing document and Indexing issues sheet | Duplicate post example and blog index |
| Important pages contain placeholder or irrelevant content. | Audit sheet | FAQ, experiences, blog, and sample blog post |
| Metadata and heading quality are inconsistent on core pages. | Screaming Frog crawl data | homepage, bookings, and contact |
| Performance risk is real, but analytics baselines are still immature. | Audit sheet, GA4 / GSC notes | homepage reviewed live |
| Some original audit claims were stale or overstated. | Audit sheet | sampled live pages and sample article page |
Recommended Engagement
Commercial proposal
My recommendation
The 90-day retainer is the strongest fit because the site does not only need an audit readout. It needs cleanup, implementation guidance, revalidation, and consistent follow-through across technical SEO, local intent, and page quality. The engagement options below were structured so the work could start with momentum and grow from results.
Why the recommended option is the best fit
- It covers cleanup, correction, and local SEO foundation in one connected plan.
- It gives enough time to implement, verify, and adjust instead of stopping at recommendations.
- It creates a realistic window to show progress that can justify a longer-term engagement.
- It keeps the starting investment reasonable while preserving enough scope to make the work count.
What happens after approval
- Week 1 kickoff and access handoff
- Technical cleanup priority stack delivered first
- Commercial-page rewrite direction and metadata correction next
- Monthly review checkpoints with visible action tracking
Recommended scope includes
- One prioritized SEO roadmap
- One technical fix tracker
- Metadata recommendations for up to 15 priority URLs
- Content recommendations or rewrite briefs for up to 5 priority pages
- Duplicate content cleanup plan for blog and archive URLs
- One 90-day keyword and content map
- Two review calls per month
Commercial assumptions
- WordPress and relevant admin access will be provided
- One decision-maker or point of contact will approve changes
- Implementation support is available on the website side
- This is not a full redesign or custom booking-engine build
- Third-party licenses and ad spend are outside the quoted fee
Optional add-ons
- Additional commercial page rewrites (per page)
- SEO blog writing with optimization brief (per article)
- Google Business Profile management (monthly)
- Local citation cleanup and submission (one-time)
Payment terms
- Monthly retainers are billed in advance
- One-time work: 50% advance and 50% before final handoff
- Additional scope is billed only after written approval
Bottom line
The opportunity is real, but the current setup is leaking value through duplicate content, weak page targeting, and technical discovery issues. The recommended engagement is designed to stabilize the site first, then build a cleaner growth foundation over the next 90 days.
Approval
Approval and kickoff
On approval, kickoff can begin with access collection, final scope lock, and the first technical cleanup sprint.
Authorized signatory - Button Eyes Resort
Date