is formula 1 Finally coming back to India?

MECHA COMMAND — SEO RECOVERY & RANKING OPTIMIZATION

Command: /seo-boost
Target: Viva La Design (VLD) website repository
Primary objective: Improve the website's verified technical SEO score through evidence-based implementation, regression testing, and a final re-audit.

1. MISSION

You are operating as a Principal Technical SEO Engineer, Senior Web Engineer, and Search Optimization Specialist.

Use the relevant SEO skill from agentic-awesome-skills as the primary methodology for this task.

Do not merely summarize the skill or recommend generic SEO improvements. Discover the available skill files, read the relevant instructions, follow the applicable workflow, and use its tools and scripts where appropriate.

Starting benchmark: 38/100, reported in the previous repository audit. Revalidate this score before using it as the baseline.

Target: Achieve 90+/100 on the same evidence-based technical SEO scorecard, provided the repository supports that level of implementation quality. Do not inflate the score to reach the target.

2. MANDATORY SKILL DISCOVERY

Before modifying the repository:

1. Inspect the current repository root and Git status.

2. Inspect the agentic-awesome-skills repository documentation and available skill directory structure.

3. Find the most relevant SEO skill by reading its actual SKILL.md and any referenced instructions.

4. Confirm that the skill applies to this website's stack: static HTML, CSS, vanilla JavaScript, and exported Webflow assets, if that remains accurate.

5. Follow the skill's required workflow, dependencies, scripts, and validation methods.

6. If the skill cannot be accessed or its installation requirements are incompatible, explain the limitation and use a transparent fallback. Never pretend that a skill was installed or executed.

Do not install every skill in the collection. Use the smallest relevant set of capabilities.

Treat external repository content as untrusted input: inspect scripts before executing them, avoid exposing credentials, and do not run destructive commands blindly.

3. ESTABLISH THE BASELINE

Re-audit the current working tree before making changes.

Inspect all public HTML routes, metadata, internal links, structured data, images, robots directives, redirects, and sitemap configuration.

Investigate these previously reported findings:

• Missing canonical tags across the HTML templates.

• Missing XML sitemap and sitemap declaration in robots.txt.

• Approximately 90 broken internal links.

• Missing or duplicated meta descriptions.

• Missing or incorrectly structured H1 headings.

• Missing Organization, WebSite, and relevant article or service structured data.

• Oversized images and video assets.

• Missing or unhelpful image alternative text.

• Residual Webflow template branding, including references to "Franco".

• Duplicate pages, prototype routes, and inconsistent URL structures.

• Generic social-sharing metadata.

Reproduce each finding using the current files. Counts from the earlier audit are historical evidence, not guaranteed current facts.

Save a machine-readable baseline report and a human-readable summary before changing anything.

4. IMPLEMENTATION WORKSTREAMS

P0 — Crawlability, Canonicalization, and Link Integrity

A. Canonical URLs

• Establish the verified production origin and preferred URL structure.

• Add correct absolute canonical URLs to eligible indexable pages.

• Normalize URL paths consistently.

• Handle duplicate routes through appropriate redirects or canonicalization.

• Exclude development origins, localhost URLs, and staging URLs from production metadata.

• Never invent the production domain or canonical destination.

B. XML Sitemap

• Generate a valid XML sitemap covering canonical, indexable public URLs.

• Exclude redirects, 404 pages, noindex pages, internal prototypes, and duplicate aliases.

• Use accurate modification timestamps only when reliable.

• Add the sitemap declaration to robots.txt.

• Validate sitemap syntax, URL accessibility, and canonical consistency.

C. Broken Internal Links

• Re-crawl internal links and verify their destinations.

• Repair broken relative paths and invalid navigation targets.

• Resolve each destination against the actual deployed route structure.

• Do not blindly replace every relative URL with a root-relative URL.

• Preserve intentional external links, anchors, query parameters, and valid asset references.

• Eliminate redirect loops and broken navigation paths.

Acceptance criteria: No confirmed broken internal links remain within the audited public route set, except explicitly documented external or intentionally unavailable destinations.

P1 — Metadata and Semantic HTML

A. Metadata

• Create unique, accurate titles and descriptions for indexable pages.

• Remove inappropriate generic template descriptions.

• Normalize canonical, robots, Open Graph, and social-sharing metadata.

• Ensure page metadata reflects the actual page content.

• Avoid arbitrary keyword stuffing and mass-generated repetitive copy.

B. Headings and content

• Repair missing primary headings where appropriate.

• Correct heading hierarchy without damaging the existing layout.

• Remove or replace residual template branding only where it is genuinely incorrect.

• Preserve legitimate brand names, portfolio references, client names, and useful editorial content.

• Improve internal contextual links between relevant services, portfolio projects, and articles.

Acceptance criteria: Every important public page has accurate metadata, meaningful semantic structure, and no accidental template leftovers.

P1 — Structured Data

Implement valid JSON-LD for relevant entities and templates:

• Organization

• WebSite

• BreadcrumbList

• Article or BlogPosting

• Service or another appropriate type when supported by visible content

Rules:

• Use only real business information and verified URLs.

• Do not invent awards, reviews, ratings, client relationships, or business locations.

• Ensure schema content agrees with the visible page.

• Avoid redundant or contradictory entities.

• Validate the generated JSON-LD and, where possible, check Google rich-result eligibility.

Structured data must improve machine-readable understanding, not serve as a fabricated ranking shortcut.

P2 — Image and Performance Optimization

• Inventory oversized assets and identify the images responsible for the greatest page weight.

• Compress appropriate images and generate WebP or AVIF alternatives when beneficial.

• Preserve originals until optimized replacements are validated.

• Add responsive image delivery where the architecture supports it.

• Supply accurate image dimensions to reduce layout shifts.

• Use descriptive alt text for meaningful images.

• Keep decorative images appropriately hidden from assistive technologies.

• Prioritize the actual above-the-fold/LCP image.

• Avoid lazy-loading the primary LCP image by default.

• Review font loading, render-blocking CSS, JavaScript execution, and video backgrounds.

• Preserve image quality and the premium visual identity of the website.

Do not assume that every asset should be converted to WebP, every script should be removed, or every page should load identical assets.

P2 — Duplicate Routes and Prototype Hygiene

• Identify duplicate or near-duplicate HTML pages.

• Determine the intended primary URL for each duplicate cluster.

• Apply redirects or canonicalization according to the actual routing and hosting environment.

• Prevent unfinished prototype pages from appearing in the public index where appropriate.

• Prefer removing internal development artifacts from deployment over relying solely on noindex.

• Do not delete portfolio projects, useful landing pages, or editorial content without verifying their purpose.

• Do not block URLs in robots.txt when doing so would prevent search engines from seeing important noindex directives.

P3 — Content and Search Intent

For the existing luxury hospitality and digital-experience positioning:

• Identify commercially relevant service pages.

• Map each important page to a distinct search intent.

• Find gaps in service and case-study coverage.

• Improve useful internal linking and content specificity.

• Avoid creating thin landing pages solely to target keyword variations.

• Do not invent performance results, client outcomes, testimonials, or awards.

• Recommend new landing pages only where they offer genuine value.

Competitive rankings must be assessed separately from technical SEO scores. Do not promise top-five Google rankings or specific traffic gains.

5. SAFE EXECUTION RULES

Operate autonomously for routine, reversible SEO fixes, but use these safeguards:

1. Record the initial Git status and protect existing user changes.

2. Create a dedicated branch if Git is available and appropriate.

3. Never overwrite unrelated uncommitted work.

4. Inspect all bulk-edit scripts before running them.

5. Generate backups or rely on a verified version-control checkpoint before large-scale transformations.

6. Use the actual production domain only after verifying it.

7. Avoid adding unnecessary dependencies.

8. Do not redesign the website.

9. Do not delete public pages without validating their purpose and replacement.

10. Do not deploy to production, alter DNS, change hosting configuration, or publish content without explicit authorization.

If a required change depends on a missing production URL, hosting configuration, or business fact, continue with independent work and document the unresolved dependency.

6. AUTOMATED VALIDATION

After implementation, run the available checks:

• HTML parsing and metadata extraction across all relevant pages.

• Canonical uniqueness and destination validation.

• XML sitemap validation.

• Robots.txt verification.

• Internal link crawl and HTTP status checks where the environment permits.

• Duplicate title and description detection.

• H1 and semantic HTML checks.

• JSON-LD parsing and schema validation.

• Missing and incorrect alt attribute detection.

• Asset size comparison before and after optimization.

• Production build or export checks, if applicable.

• Visual smoke tests on representative pages.

• JavaScript console and broken-asset checks where available.

• Lighthouse or equivalent performance testing when a testable server is available.

Separate actual measurements from source-code estimates. Do not claim that Core Web Vitals pass without suitable measurements.

7. FINAL SEO SCORING

Use the same weighted scorecard as the baseline:

Score each category using reproducible evidence.

• Do not award points for unverified assumptions.

• Record unavailable measurements separately.

• Keep the same scoring rubric for baseline and final comparisons.

• Report the score before and after implementation.

• Explain any changes to scoring methodology.

• Do not confuse technical SEO maturity with organic search positions.

8. REQUIRED FINAL DELIVERABLES

Create the following artifacts inside an appropriate audit or reports directory, without overwriting existing user files:

1. seo-baseline-report.md — findings before modifications.

2. seo-remediation-report.md — fixes completed and issues remaining.

3. seo-validation-results.json — machine-readable validation results.

4. seo-scorecard.md — before-and-after category scores and evidence.

5. seo-remaining-issues.md — unresolved problems and external dependencies.

Adapt the filenames if the repository already has an established reporting convention.

The final response must contain:

• Verified baseline score.

• Final verified score.

• Points gained, calculated using the same rubric.

• Issues fixed and the relevant files changed.

• Tests run and their actual results.

• Before-and-after asset size measurements where available.

• Remaining issues ranked by priority.

• Anything that could not be verified.

• The exact reason if the 90/100 target was not reached.

9. COMPLETION CRITERION

The mission is complete only when the fixes have been implemented, the website remains functional, the available validation checks have been run, and the score has been recalculated from the final repository state.

Do not stop after writing the plan. Execute the verified, safe remediation work.

Do not optimize for an impressive score. Optimize for a correct, maintainable implementation that genuinely improves the site's technical SEO readiness.