Skip to content

Latest commit

 

History

History
669 lines (558 loc) · 21 KB

File metadata and controls

669 lines (558 loc) · 21 KB

You are working inside the existing ProxyTechSupport website codebase.

TASK: Create a complete global AI/ML SEO cluster for proxytechsupport.com.

VERY IMPORTANT RULES:

  1. Do not remove, rename, overwrite, or break any existing page, route, component, layout, CSS, metadata, sitemap entry, or existing internal link.

  2. This is a pure new addition and expansion.

  3. Before generating content, first create a clear physical file/page plan.

  4. Do not attempt to generate all pages in memory at once.

  5. Create physical files in batches.

  6. Add one page at a time, save it, then continue.

  7. Every new page must be internally linked to its correct parent, child, and related pages.

  8. Every page must support SEO indexing, agentic bot indexing, AI search visibility, and normal Google indexing.

  9. Every page must include unique title, meta description, canonical URL, H1, H2 structure, FAQ schema, service schema where appropriate, breadcrumb schema, and internal links.

  10. Do not create thin pages. Each page should have useful, technically strong, business-focused content.

  11. Do not duplicate the same content across country/city/role/technology pages. Reuse structure, but rewrite context and examples.

  12. Existing AI/ML pages must be connected into the new cluster instead of being ignored.

  13. Existing pages such as /ai-ml-job-support/, /ai-ml-job-support-guide/, /mlops-job-support-guide/, /rag-agentic-ai-job-support-guide/, /genai-interview-support-guide/, /ai-ml-proxy-interview-support/, /mlops-proxy-interview-support/, /data-science-job-support/, /agentic-ai-ml-job-support/, /ai-workflow-automation-pipeline-job-support/, and /dotnet-ai-ml-job-support/ should remain untouched unless adding safe internal links is required.

  14. If a route already exists, do not recreate it. Instead, enhance linking only if safe.

  15. Update sitemap generation/config only by adding new URLs. Do not remove existing URLs.

  16. Update navigation only if there is already a safe cluster/technology/location navigation pattern.

  17. Build the cluster with clear funnel logic: Global Hub → Country Pages → City Pages → Technology Pages → Role Pages → Interview Support Pages → Candidate Marketing Pages → Contact/WhatsApp CTA.

  18. Each page must naturally target job support, real-time project support, production issue help, interview support, profile/candidate marketing, and interview scheduling where relevant.

  19. Do not use unethical or risky wording. Use professional terms such as real-time job support, technical interview support, project onboarding help, production issue support, profile positioning, candidate marketing, interview preparation, and live technical mentoring.

  20. Keep CTAs business-focused:

    • Get AI/ML project support
    • Get interview-ready
    • Get profile positioned for AI/ML roles
    • Get help with production AI issues
    • Talk to ProxyTechSupport

EXISTING CONTEXT: The site already has broad service pages, country job support pages, proxy interview pages, .NET cluster pages, Workday cluster pages, UiPath cluster pages, job application/candidate marketing pages, and some AI/ML starter pages. The new AI/ML cluster must connect with these existing funnels.

MAIN EXISTING AI/ML PAGES TO CONNECT:

  • /ai-ml-job-support/
  • /ai-ml-job-support-guide/
  • /data-science-job-support/
  • /ai-workflow-automation-pipeline-job-support/
  • /agentic-ai-ml-job-support/
  • /agentic-ai-rag-mlops-job-support-usa/
  • /agentic-ai-ml-job-support-usa/
  • /ai-workflow-automation-pipeline-job-support-usa/
  • /ai-ml-job-support-canada/
  • /ai-ml-devops-sre-job-support-ireland/
  • /germany-ai-ml-data-support-guide/
  • /europe-ai-ml-rag-mlops-support-guide/
  • /ai-ml-devops-sre-job-support-texas/
  • /ai-ml-proxy-interview-support/
  • /mlops-proxy-interview-support/
  • /genai-interview-support-guide/
  • /mlops-job-support-guide/
  • /rag-agentic-ai-job-support-guide/
  • /ai-ml-data-science-proxy-job-support/
  • /dotnet-ai-ml-job-support/
  • /semantic-kernel-job-support/
  • /azure-openai-dotnet-job-support/
  • /rag-dotnet-job-support/
  • /vector-search-dotnet-job-support/
  • /ai-agents-dotnet-job-support/
  • /azure-ai-search-dotnet-job-support/
  • /openai-sdk-dotnet-job-support/
  • /dotnet-ai-interview-proxy-support/

NEW AI/ML CLUSTER STRUCTURE:

PHASE 1 — GLOBAL HUB AND CORE PAGES

Create these new pages:

  1. /global-ai-ml-job-support/ Purpose: Main global AI/ML hub. Connect to:
  • /ai-ml-job-support/
  • /ai-ml-job-support-guide/
  • /mlops-job-support-guide/
  • /rag-agentic-ai-job-support-guide/
  • /genai-interview-support-guide/
  • all country AI/ML pages
  • all technology AI/ML pages
  • all role AI/ML pages
  • AI/ML interview and candidate marketing pages
  1. /ai-ml-production-support/ Purpose: Production AI/ML issue support. Target keywords: AI ML production support, model deployment issue support, LLM production issue help, RAG pipeline debugging, MLOps production support. Connect to:
  • /production-issue-support/
  • /production-issue-support-for-it-professionals/
  • /mlops-job-support-guide/
  • /rag-agentic-ai-job-support-guide/
  1. /ai-ml-project-onboarding-support/ Purpose: Help candidates who joined AI/ML projects and need onboarding help. Target keywords: AI ML project onboarding help, new AI engineer job support, GenAI project onboarding, MLOps onboarding help. Connect to:
  • /client-call-and-standup-support-guide/
  • /real-time-it-job-support-guide/
  • /global-ai-ml-job-support/
  1. /ai-ml-client-call-standup-support/ Purpose: Client call, standup, sprint, architecture discussion support for AI/ML engineers. Connect to:
  • /client-call-and-standup-support-guide/
  • /ai-ml-project-onboarding-support/
  • /ai-ml-production-support/
  1. /ai-ml-profile-positioning-support/ Purpose: AI/ML profile positioning and candidate marketing. Connect to:
  • /job-application-candidate-marketing/
  • /resume-linkedin-optimization-for-developers/
  • /global-ai-ml-job-support/
  • /get-ai-ml-interview-scheduled/

PHASE 2 — COUNTRY-WISE AI/ML JOB SUPPORT PAGES

Create these country pages:

  1. /usa-ai-ml-job-support/
  2. /canada-ai-ml-job-support/
  3. /uk-ai-ml-job-support/
  4. /ireland-ai-ml-job-support/
  5. /germany-ai-ml-job-support/
  6. /netherlands-ai-ml-job-support/
  7. /france-ai-ml-job-support/
  8. /sweden-ai-ml-job-support/
  9. /switzerland-ai-ml-job-support/
  10. /australia-ai-ml-job-support/
  11. /new-zealand-ai-ml-job-support/
  12. /singapore-ai-ml-job-support/
  13. /hong-kong-ai-ml-job-support/
  14. /uae-ai-ml-job-support/
  15. /saudi-arabia-ai-ml-job-support/
  16. /europe-ai-ml-job-support/

Each country page must include:

  • Country-specific intro
  • AI/ML job support use cases
  • GenAI, RAG, MLOps, data science, Python, cloud AI, LLM support
  • Interview support section
  • Candidate marketing section
  • Internal links to top city pages in that country
  • Internal links to AI/ML technology pages
  • CTA to contact ProxyTechSupport

PHASE 3 — USA CITY AI/ML PAGES

Create:

  1. /new-york-ai-ml-job-support/
  2. /san-francisco-ai-ml-job-support/
  3. /san-jose-ai-ml-job-support/
  4. /seattle-ai-ml-job-support/
  5. /boston-ai-ml-job-support/
  6. /dallas-ai-ml-job-support/
  7. /austin-ai-ml-job-support/
  8. /chicago-ai-ml-job-support/
  9. /atlanta-ai-ml-job-support/
  10. /houston-ai-ml-job-support/
  11. /los-angeles-ai-ml-job-support/
  12. /washington-dc-ai-ml-job-support/
  13. /jersey-city-ai-ml-job-support/
  14. /charlotte-ai-ml-job-support/
  15. /phoenix-ai-ml-job-support/
  16. /tampa-ai-ml-job-support/

Each USA city page must link to:

  • /usa-ai-ml-job-support/
  • /global-ai-ml-job-support/
  • relevant role pages
  • relevant technology pages
  • /ai-ml-interview-proxy-support-usa/
  • /job-application-candidate-marketing-usa/

PHASE 4 — CANADA CITY AI/ML PAGES

Create:

  1. /toronto-ai-ml-job-support/
  2. /vancouver-ai-ml-job-support/
  3. /calgary-ai-ml-job-support/
  4. /montreal-ai-ml-job-support/
  5. /ottawa-ai-ml-job-support/

Each Canada city page must link to:

  • /canada-ai-ml-job-support/
  • /ai-ml-job-support-canada/
  • /canada-proxy-job-support-guide/
  • /canada-interview-proxy-support-guide/
  • /job-application-candidate-marketing-canada/

PHASE 5 — UK AND IRELAND CITY AI/ML PAGES

Create:

  1. /london-ai-ml-job-support/
  2. /manchester-ai-ml-job-support/
  3. /birmingham-ai-ml-job-support/
  4. /dublin-ai-ml-job-support/
  5. /cork-ai-ml-job-support/

Each page must link to:

  • /uk-ai-ml-job-support/ or /ireland-ai-ml-job-support/
  • /global-ai-ml-job-support/
  • /job-application-candidate-marketing-uk/ or /job-application-candidate-marketing-ireland/
  • /get-ai-ml-interview-scheduled-uk/ or /get-ai-ml-interview-scheduled-ireland/

PHASE 6 — EUROPE CITY AI/ML PAGES

Create:

  1. /berlin-ai-ml-job-support/
  2. /munich-ai-ml-job-support/
  3. /frankfurt-ai-ml-job-support/
  4. /hamburg-ai-ml-job-support/
  5. /amsterdam-ai-ml-job-support/
  6. /rotterdam-ai-ml-job-support/
  7. /paris-ai-ml-job-support/
  8. /stockholm-ai-ml-job-support/
  9. /zurich-ai-ml-job-support/
  10. /geneva-ai-ml-job-support/

Each page must link to:

  • matching country page
  • /europe-ai-ml-job-support/
  • /europe-ai-ml-rag-mlops-support-guide/
  • /job-application-candidate-marketing-europe/

PHASE 7 — AUSTRALIA, NEW ZEALAND, ASIA, AND GULF CITY AI/ML PAGES

Create:

  1. /sydney-ai-ml-job-support/
  2. /melbourne-ai-ml-job-support/
  3. /brisbane-ai-ml-job-support/
  4. /perth-ai-ml-job-support/
  5. /auckland-ai-ml-job-support/
  6. /wellington-ai-ml-job-support/
  7. /singapore-ai-ml-job-support/
  8. /hong-kong-ai-ml-job-support/
  9. /dubai-ai-ml-job-support/
  10. /abu-dhabi-ai-ml-job-support/
  11. /riyadh-ai-ml-job-support/
  12. /jeddah-ai-ml-job-support/

Each page must link to:

  • matching country page
  • /global-ai-ml-job-support/
  • /ai-ml-production-support/
  • /ai-ml-profile-positioning-support/
  • matching candidate marketing page if it exists

PHASE 8 — AI/ML TECHNOLOGY PAGES

Create:

  1. /python-ai-ml-job-support/
  2. /python-genai-job-support/
  3. /llm-job-support/
  4. /generative-ai-job-support/
  5. /rag-job-support/
  6. /agentic-ai-job-support/
  7. /langchain-job-support/
  8. /langgraph-job-support/
  9. /crewai-job-support/
  10. /autogen-job-support/
  11. /openai-api-job-support/
  12. /azure-openai-job-support/
  13. /aws-bedrock-job-support/
  14. /google-vertex-ai-job-support/
  15. /hugging-face-job-support/
  16. /transformers-job-support/
  17. /pytorch-job-support/
  18. /tensorflow-job-support/
  19. /scikit-learn-job-support/
  20. /mlops-job-support/
  21. /kubeflow-job-support/
  22. /mlflow-job-support/
  23. /airflow-ml-pipeline-job-support/
  24. /databricks-ml-job-support/
  25. /snowflake-cortex-ai-job-support/
  26. /vector-database-job-support/
  27. /pinecone-job-support/
  28. /qdrant-job-support/
  29. /weaviate-job-support/
  30. /chromadb-job-support/
  31. /llm-evaluation-job-support/
  32. /prompt-engineering-job-support/
  33. /fine-tuning-job-support/
  34. /lora-qlora-job-support/
  35. /model-deployment-job-support/
  36. /model-monitoring-job-support/
  37. /ai-production-debugging-support/
  38. /computer-vision-job-support/
  39. /nlp-job-support/
  40. /recommendation-system-job-support/
  41. /time-series-forecasting-job-support/
  42. /ai-api-integration-job-support/
  43. /ai-workflow-orchestration-job-support/
  44. /multi-agent-ai-job-support/
  45. /mcp-server-ai-job-support/
  46. /ai-security-governance-job-support/
  47. /responsible-ai-job-support/

Each technology page must include:

  • What the technology is used for in real projects
  • Common production problems
  • Interview questions covered
  • Real-time job support scenarios
  • Related technologies
  • Links to role pages
  • Links to country pages
  • CTA to AI/ML job support and interview support

PHASE 9 — ROLE-WISE AI/ML PAGES

Create:

  1. /ai-engineer-job-support/
  2. /machine-learning-engineer-job-support/
  3. /genai-engineer-job-support/
  4. /llm-engineer-job-support/
  5. /mlops-engineer-job-support/
  6. /data-scientist-job-support/
  7. /nlp-engineer-job-support/
  8. /computer-vision-engineer-job-support/
  9. /ai-solutions-architect-job-support/
  10. /ai-platform-engineer-job-support/
  11. /ai-product-engineer-job-support/
  12. /ai-automation-engineer-job-support/
  13. /prompt-engineer-job-support/
  14. /applied-ai-engineer-job-support/
  15. /ai-research-engineer-job-support/
  16. /data-engineer-ai-ml-job-support/
  17. /cloud-ai-engineer-job-support/
  18. /ai-devops-engineer-job-support/
  19. /rag-engineer-job-support/
  20. /agentic-ai-engineer-job-support/

Each role page must include:

  • Role-specific project support
  • Real production tasks
  • Interview support
  • Candidate marketing
  • Technologies used in that role
  • Links to relevant technology pages
  • Links to global and country AI/ML pages

PHASE 10 — AI/ML INTERVIEW SUPPORT PAGES

Create:

  1. /ai-ml-interview-proxy-support-usa/
  2. /ai-ml-interview-proxy-support-canada/
  3. /ai-ml-interview-proxy-support-uk/
  4. /ai-ml-interview-proxy-support-australia/
  5. /ai-ml-interview-proxy-support-europe/
  6. /ai-ml-interview-proxy-support-singapore/
  7. /genai-interview-proxy-support/
  8. /llm-interview-proxy-support/
  9. /rag-interview-proxy-support/
  10. /mlops-interview-proxy-support/
  11. /data-science-interview-proxy-support/
  12. /machine-learning-engineer-interview-proxy-support/
  13. /ai-architect-interview-proxy-support/
  14. /ai-platform-engineer-interview-proxy-support/
  15. /agentic-ai-interview-proxy-support/
  16. /langchain-langgraph-interview-support/
  17. /azure-openai-interview-support/
  18. /aws-bedrock-interview-support/
  19. /python-ai-ml-interview-support/

Each interview page must link to:

  • /ai-ml-proxy-interview-support/
  • /mlops-proxy-interview-support/
  • /genai-interview-support-guide/
  • /final-round-interview-support-guide/
  • /technical-interview-support-usa-guide/
  • matching role pages
  • matching technology pages

PHASE 11 — AI/ML INTERVIEW SCHEDULED FUNNEL PAGES

Create:

  1. /get-ai-ml-interview-scheduled/
  2. /get-ai-ml-interview-scheduled-usa/
  3. /get-ai-ml-interview-scheduled-canada/
  4. /get-ai-ml-interview-scheduled-uk/
  5. /get-ai-ml-interview-scheduled-australia/
  6. /get-ai-ml-interview-scheduled-ireland/
  7. /get-ai-ml-interview-scheduled-germany/
  8. /get-ai-ml-interview-scheduled-singapore/
  9. /get-ai-ml-interview-scheduled-uae/
  10. /get-genai-interview-scheduled/
  11. /get-mlops-interview-scheduled/
  12. /get-data-science-interview-scheduled/
  13. /get-llm-engineer-interview-scheduled/
  14. /get-ai-architect-interview-scheduled/

Each page must target candidates who are getting no calls or need interviews scheduled for AI/ML roles. Connect to candidate marketing pages and interview proxy pages.

PHASE 12 — AI/ML CANDIDATE MARKETING PAGES

Create:

  1. /ai-ml-candidate-marketing/
  2. /ai-ml-candidate-marketing-usa/
  3. /ai-ml-candidate-marketing-canada/
  4. /ai-ml-candidate-marketing-uk/
  5. /ai-ml-candidate-marketing-australia/
  6. /ai-ml-candidate-marketing-germany/
  7. /ai-ml-candidate-marketing-ireland/
  8. /ai-ml-candidate-marketing-singapore/
  9. /ai-ml-candidate-marketing-uae/
  10. /genai-candidate-marketing/
  11. /mlops-candidate-marketing/
  12. /data-science-candidate-marketing/
  13. /ai-engineer-profile-positioning/
  14. /ml-engineer-profile-positioning/
  15. /llm-engineer-profile-positioning/
  16. /ai-architect-profile-positioning/

Each page must connect to:

  • /job-application-candidate-marketing/
  • relevant country candidate marketing pages
  • /ai-ml-profile-positioning-support/
  • /get-ai-ml-interview-scheduled/
  • relevant role pages

PHASE 13 — INDUSTRY AI/ML PAGES

Create:

  1. /healthcare-ai-ml-job-support/
  2. /fintech-ai-ml-job-support/
  3. /banking-ai-ml-job-support/
  4. /insurance-ai-ml-job-support/
  5. /retail-ai-ml-job-support/
  6. /ecommerce-ai-ml-job-support/
  7. /telecom-ai-ml-job-support/
  8. /manufacturing-ai-ml-job-support/
  9. /pharma-ai-ml-job-support/
  10. /supply-chain-ai-ml-job-support/
  11. /cybersecurity-ai-ml-job-support/
  12. /enterprise-ai-ml-job-support/

Each industry page must include:

  • Industry-specific AI/ML use cases
  • Production problems
  • Interview topics
  • AI/ML project support
  • Internal links to technology pages and role pages

PHASE 14 — AI/ML KNOWLEDGE BASE AND GUIDE PAGES

Create:

  1. /what-is-ai-ml-job-support/
  2. /how-ai-ml-job-support-works/
  3. /ai-ml-production-issue-support-guide/
  4. /ai-ml-project-onboarding-guide/
  5. /rag-production-support-guide/
  6. /llm-application-support-guide/
  7. /mlops-production-support-guide/
  8. /ai-model-deployment-support-guide/
  9. /ai-model-monitoring-support-guide/
  10. /ai-ml-interview-preparation-guide/
  11. /genai-system-design-interview-guide/
  12. /rag-system-design-interview-guide/
  13. /mlops-system-design-interview-guide/
  14. /ai-ml-resume-profile-positioning-guide/
  15. /ai-engineer-job-search-guide/
  16. /ml-engineer-job-search-guide/
  17. /genai-engineer-job-search-guide/
  18. /data-scientist-job-search-guide/

These pages should be educational and should link to commercial pages naturally.

PHASE 15 — AI/ML COMPARISON AND PROBLEM-SOLUTION PAGES

Create:

  1. /ai-ml-job-support-vs-interview-support/
  2. /genai-job-support-vs-mlops-job-support/
  3. /rag-vs-fine-tuning-job-support/
  4. /langchain-vs-langgraph-job-support/
  5. /azure-openai-vs-aws-bedrock-job-support/
  6. /vector-database-selection-for-rag/
  7. /why-ai-ml-resume-gets-no-calls/
  8. /why-ai-ml-interviews-are-failing/
  9. /how-to-get-ai-ml-interviews-scheduled/
  10. /how-to-survive-new-ai-ml-job/
  11. /how-to-handle-ai-ml-production-issues/
  12. /how-to-explain-rag-project-in-interview/
  13. /how-to-explain-mlops-project-in-interview/
  14. /how-to-explain-genai-project-in-interview/
  15. /how-to-explain-agentic-ai-project-in-interview/

These pages should capture high-intent problem searches.

FINAL INTERNAL LINKING REQUIREMENTS:

Global Hub: /global-ai-ml-job-support/ must link to:

  • all country AI/ML pages
  • all major technology pages
  • all role pages
  • AI/ML interview pages
  • AI/ML candidate marketing pages
  • AI/ML production support
  • AI/ML onboarding support

Country Pages: Each country page must link to:

  • /global-ai-ml-job-support/
  • its city pages
  • role pages
  • technology pages
  • interview page for that country
  • candidate marketing page for that country

City Pages: Each city page must link to:

  • matching country page
  • /global-ai-ml-job-support/
  • 5–8 relevant technology pages
  • 3–5 role pages
  • interview support page
  • candidate marketing page

Technology Pages: Each technology page must link to:

  • /global-ai-ml-job-support/
  • /ai-ml-production-support/
  • relevant role pages
  • relevant interview support pages
  • country pages

Role Pages: Each role page must link to:

  • /global-ai-ml-job-support/
  • relevant technology pages
  • interview page for that role
  • candidate marketing/profile positioning page
  • country pages

Interview Pages: Each interview page must link to:

  • /ai-ml-proxy-interview-support/
  • /genai-interview-support-guide/
  • /mlops-proxy-interview-support/
  • relevant role pages
  • relevant technology pages
  • get interview scheduled pages

Candidate Marketing Pages: Each candidate marketing page must link to:

  • /job-application-candidate-marketing/
  • /ai-ml-profile-positioning-support/
  • /get-ai-ml-interview-scheduled/
  • role pages
  • country pages

CONTENT QUALITY REQUIREMENTS: Every page must include:

  • Strong H1
  • 5–8 H2 sections
  • Short intro
  • Real project support examples
  • Production issue examples
  • Interview support examples
  • Candidate positioning section where relevant
  • FAQ section with 5–7 FAQs
  • CTA section
  • Related pages section
  • Breadcrumbs
  • JSON-LD schema
  • Unique meta title under 60 characters
  • Unique meta description under 155 characters
  • Canonical URL
  • Clean slug
  • No keyword stuffing
  • No copied repeated paragraphs

TECHNICAL EXECUTION:

  1. Inspect current routing/page generation pattern.

  2. Identify how existing clusters are implemented.

  3. Reuse existing layout/components where safe.

  4. Create a data-driven page configuration if the site already uses one.

  5. If the site uses static files, create one file per page.

  6. Generate pages in batches:

    • Batch 1: Global + core pages
    • Batch 2: Country pages
    • Batch 3: USA city pages
    • Batch 4: Canada/UK/Ireland/Europe city pages
    • Batch 5: Australia/NZ/Asia/Gulf city pages
    • Batch 6: Technology pages
    • Batch 7: Role pages
    • Batch 8: Interview pages
    • Batch 9: Interview scheduled pages
    • Batch 10: Candidate marketing pages
    • Batch 11: Industry pages
    • Batch 12: Knowledge base/comparison pages
  7. After each batch, run build/lint/typecheck if available.

  8. Fix only issues caused by new additions.

  9. Do not refactor unrelated code.

  10. Update sitemap only by adding new URLs.

  11. Add internal links safely.

  12. Provide final summary:

    • Pages created
    • Files changed
    • Sitemap entries added
    • Internal linking completed
    • Build/lint result
    • Any skipped routes because they already existed

EXPECTED RESULT: A complete AI/ML global cluster covering:

  • Global AI/ML support
  • Country-wise AI/ML support
  • City-wise AI/ML support
  • Technology-wise AI/ML support
  • Role-wise AI/ML support
  • AI/ML interview support
  • AI/ML interview scheduled funnel
  • AI/ML candidate marketing
  • AI/ML production support
  • AI/ML onboarding support
  • AI/ML industry pages
  • AI/ML knowledge base pages

Do this carefully as an add-only SEO expansion without breaking existing pages.