Skip to content

DOT_NET_CLUSTER.md

Latest commit

 

History

History
1611 lines (1219 loc) · 40.1 KB

DOT_NET_CLUSTER.md

File metadata and controls

1611 lines (1219 loc) · 40.1 KB

You are working on the Proxy Tech Support website.

Website: https://proxytechsupport.com Business Phone / WhatsApp CTA: +91 96606 14469 Main service goal: generate high-intent traffic for .NET job support, .NET Azure job support, .NET AI/ML job support, .NET project support, .NET interview proxy, proxy interview support, and real-time job support for developers in USA, Canada, UK, Ireland, Europe, Australia, New Zealand, Singapore, UAE, and Saudi Arabia.

VERY IMPORTANT EXECUTION RULE — READ FIRST:

DO NOT generate all pages in memory first.

DO NOT create one giant content object.

DO NOT plan all page content in RAM and then write later.

DO NOT attempt to hold 50+ page bodies in memory.

DO NOT refactor the existing website.

DO NOT touch existing service pages except adding safe internal links/CTA sections where specifically required.

You must work in a file-by-file, chunk-by-chunk method.

CRITICAL TOP INSTRUCTION — PURE ADDITION ONLY, NO BREAKING EXISTING WEBSITE

This task is a pure additive SEO cluster expansion for the existing Proxy Tech Support website.

You must NOT remove, rewrite, rename, delete, refactor, or break any existing page, route, component, service page, blog page, interview page, navigation item, sitemap entry, metadata, schema, design system, layout, CSS, or existing business funnel.

This is strictly a new Modern .NET + Azure + AI/ML job support cluster addition.

Before making changes:

  1. Inspect the existing project structure.

  2. Identify existing routing/page conventions.

  3. Identify existing SEO/meta/schema conventions.

  4. Identify existing sitemap/navigation conventions.

  5. Identify existing service funnel pages.

  6. Identify whether any existing .NET page already exists.

  7. If an existing .NET page exists, do NOT overwrite it. Instead:

    • preserve it fully
    • add a small safe internal link section pointing to the new parent cluster page
    • create the new cluster pages separately

ZERO BREAKAGE RULES:

  • Do not delete any file.
  • Do not rename any existing file.
  • Do not move any existing file.
  • Do not replace existing content.
  • Do not remove existing imports.
  • Do not change global layout unless only adding one safe link/section.
  • Do not change current service pricing.
  • Do not alter existing interview proxy/profile engineering/job support wording except adding small internal links.
  • Do not modify working components unless necessary for adding links.
  • Do not change homepage design structure. Only add one small new section if safe.
  • Do not create duplicate route conflicts.
  • Do not overwrite existing slug files.
  • Do not break current build.
  • Do not remove existing sitemap URLs.
  • Do not remove existing JSON-LD/schema.
  • Do not remove existing Open Graph or Twitter metadata.
  • Do not touch unrelated clusters.

If any target URL already exists:

  • Do not overwrite it blindly.
  • Read the file first.
  • Preserve existing content.
  • Add only missing .NET cluster internal links and metadata if safe.
  • If unsafe, create a note in the final report and skip destructive changes.

MEMORY-SAFE EXECUTION RULE:

Do NOT generate all pages in memory first.

Do NOT create one giant content object.

Do NOT generate 100+ pages in RAM.

You must create physical planning/inventory files first, then generate one page at a time, save it physically, update inventory status, and only then continue to the next page.

Use this workflow:

  1. Create /content-plans/modern-dotnet-azure-ai-cluster-plan.md
  2. Create /content-plans/modern-dotnet-page-inventory.json
  3. Store all URL/title/meta/keyword/linking plan in the inventory file.
  4. Start with the parent page.
  5. Generate one page only.
  6. Save the page file.
  7. Update inventory status to completed.
  8. Move to the next page.
  9. Every 10 pages, verify routes, file existence, metadata, internal links, duplicate slugs, and build safety.
  10. Continue from inventory if interrupted.

NEW CLUSTER FUNNEL REQUIREMENT:

The new pages must create a clear internal SEO and conversion funnel.

Funnel structure:

Homepage / existing landing page → Modern .NET Azure AI Job Support parent page → Country .NET job support pages → City .NET job support pages → Technology-specific .NET support pages → Azure .NET support pages → AI/ML .NET support pages → Interview proxy support pages → WhatsApp / Call CTA

Main parent page: /modern-dotnet-azure-ai-job-support/

This parent page must act as the central hub for:

  • .NET job support
  • ASP.NET Core job support
  • .NET Azure job support
  • .NET AI/ML job support
  • .NET Aspire job support
  • Semantic Kernel job support
  • Azure AI Foundry .NET support
  • RAG in .NET support
  • AI agents in .NET support
  • full-stack .NET support
  • .NET interview proxy support
  • legacy .NET modernization support

INTERNAL LINKING REQUIREMENT:

All new pages must be interlinked with each other in a logical cluster.

Every new page must link back to:

  1. /modern-dotnet-azure-ai-job-support/
  2. /dotnet-azure-job-support/ where relevant
  3. /dotnet-ai-ml-job-support/ where relevant
  4. /dotnet-interview-proxy-support/ where relevant
  5. at least 3–6 related pages from the new .NET cluster

Parent page must link to:

  • all country pages
  • main city pages
  • all core tech pages
  • all Azure pages
  • all AI/ML pages
  • all cloud-native pages
  • all full-stack pages
  • all modernization pages
  • all interview support pages

Country pages must link to:

  • parent page
  • relevant city pages
  • ASP.NET Core job support
  • .NET Azure job support
  • .NET AI/ML job support
  • .NET interview proxy support

City pages must link to:

  • parent page
  • related country page
  • ASP.NET Core job support
  • .NET Azure job support
  • full-stack .NET job support
  • .NET interview proxy support

Technology pages must link to:

  • parent page
  • .NET Azure job support
  • .NET AI/ML job support if relevant
  • ASP.NET Core job support if relevant
  • .NET interview proxy support
  • 3–5 closely related tech pages

AI pages must link to:

  • parent page
  • .NET AI/ML job support
  • Semantic Kernel job support
  • Azure AI Foundry .NET job support
  • Azure OpenAI .NET job support
  • RAG in .NET job support
  • AI Agents in .NET job support
  • OpenAI SDK .NET job support

Azure pages must link to:

  • parent page
  • .NET Azure job support
  • Azure Functions .NET job support
  • Azure App Service .NET job support
  • Azure DevOps .NET job support
  • Azure Key Vault .NET job support
  • .NET interview proxy support

Interview pages must link to:

  • parent page
  • ASP.NET Core job support
  • .NET Azure job support
  • .NET AI/ML job support
  • full-stack .NET job support
  • job support main service page if exists

ENTRY POINT REQUIREMENT:

Create at least one clear entry point from the existing website into the new cluster.

Preferred entry points:

  1. Homepage / main landing page
  2. Existing technologies page
  3. Existing job support service page
  4. Existing interview proxy service page
  5. Existing .NET page if it already exists

Add only safe, small sections or links. Do not redesign the existing pages.

Homepage section suggestion:

Title: Modern .NET, Azure & AI Job Support

Short text: Get real-time .NET job support for ASP.NET Core, Azure, .NET 10, Semantic Kernel, Azure AI Foundry, RAG, AI agents, microservices, full-stack .NET, and production project issues.

CTA: Explore .NET Job Support

Link: /modern-dotnet-azure-ai-job-support/

SEO + AI SEARCH + AGENTIC BOT INDEXING REQUIREMENTS:

Each new page must be optimized for:

  • Google indexing
  • Bing indexing
  • AI search engines
  • ChatGPT/Gemini/Perplexity style answer engines
  • agentic bots
  • social media previews
  • rich snippets
  • local/country/city search intent
  • service buyer-intent queries

For every new page, implement where supported by the project:

  1. Unique SEO title
  2. Unique meta description
  3. Canonical URL
  4. Open Graph title
  5. Open Graph description
  6. Open Graph type
  7. Open Graph URL
  8. Twitter card title
  9. Twitter card description
  10. Breadcrumbs
  11. FAQ schema JSON-LD
  12. Service schema JSON-LD
  13. LocalBusiness or Organization schema where appropriate
  14. WebPage schema
  15. ItemList schema on hub/listing pages where appropriate
  16. Article schema for interview question pages
  17. Speakable-style concise answer blocks only if existing project supports it
  18. Clean H1/H2/H3 hierarchy
  19. Table of contents on long parent/interview pages if existing style supports it
  20. Related pages section
  21. Clear CTA section
  22. Updated sitemap entry if sitemap is manual
  23. robots/indexing compatibility
  24. noindex must NOT be used on these pages

JSON-LD REQUIREMENTS:

Use JSON-LD only in the same style already used by the website. Do not create incompatible schema implementation.

For service pages, include:

  • Service schema
  • FAQPage schema
  • BreadcrumbList schema
  • Organization schema reference if existing

For country/city pages, include:

  • Service schema
  • FAQPage schema
  • BreadcrumbList schema
  • areaServed with country/city where appropriate

For parent hub page, include:

  • WebPage schema
  • Service schema
  • ItemList schema for cluster links
  • FAQPage schema
  • BreadcrumbList schema

For interview question pages, include:

  • Article schema
  • FAQPage schema
  • BreadcrumbList schema

Schema must be valid JSON-LD. Do not include fake ratings, fake reviews, fake aggregateRating, or fake testimonials.

SOCIAL MEDIA META REQUIREMENTS:

Each page should have social preview metadata if project supports it:

  • og:title
  • og:description
  • og:type
  • og:url
  • og:image only if existing site has a default image pattern
  • twitter:card
  • twitter:title
  • twitter:description
  • twitter:image only if existing pattern exists

Do not invent missing image assets. Use existing default OG image if available.

CONTENT INDEXING BLOCK REQUIREMENT:

Add one concise answer-style block near the top of each page for AI search extraction.

Example format:

“Quick Answer: We provide real-time .NET job support for developers working on ASP.NET Core, Azure, .NET 10, Semantic Kernel, Azure AI Foundry, RAG, AI agents, microservices, debugging, deployment, and production project tasks. Support is available remotely through WhatsApp/Call at +91 96606 14469.”

This block must be unique per page and match that page’s topic/location/technology.

CONTENT QUALITY REQUIREMENTS:

Every page must be unique and useful.

Do not create doorway spam pages.

Do not create only city-name swapped pages.

Each page needs:

  • unique local/technology angle
  • real project problems
  • specific .NET/Azure/AI tasks
  • support workflow
  • interview support connection
  • CTA
  • FAQ
  • related links

Main CTA: WhatsApp / Call: +91 96606 14469

Do not guarantee jobs. Do not guarantee interview selection. Do not claim official Microsoft partnership. Do not claim certified Microsoft partner unless already shown on site. Do not add fake client logos. Do not add fake testimonials.

FINAL REPORT REQUIREMENT:

At the end, provide a final implementation report with:

  1. Total new pages created
  2. All new page URLs
  3. Existing files touched
  4. What was added to homepage/landing page
  5. What was added to existing .NET page if any
  6. Sitemap status
  7. JSON-LD/schema status
  8. Open Graph/Twitter metadata status
  9. Internal linking summary
  10. Build result
  11. Lint result if available
  12. Any skipped pages or route conflicts
  13. Any manual follow-up needed

START BY INSPECTING THE PROJECT. DO NOT MODIFY ANY EXISTING FILE UNTIL YOU UNDERSTAND THE ROUTING, SEO, SITEMAP, AND PAGE COMPONENT STRUCTURE.

Required workflow:

  1. First inspect the existing project structure.

  2. Identify the framework, routing pattern, content/page pattern, components, SEO metadata pattern, sitemap pattern, and existing service page style.

  3. Create a physical planning file first: /content-plans/modern-dotnet-azure-ai-cluster-plan.md

  4. Create a physical page inventory file: /content-plans/modern-dotnet-page-inventory.json

  5. Add all planned URLs, titles, meta titles, meta descriptions, target keywords, and internal links into the inventory file only.

  6. After the inventory file is saved, start page generation.

  7. Generate only ONE page at a time.

  8. For each page:

    • Open the inventory.
    • Pick the next page.
    • Create the physical page file.
    • Write that page content into the file.
    • Save the file.
    • Add metadata/schema if the project supports it.
    • Add internal links only needed for that page.
    • Verify build/lint impact for that file if possible.
    • Mark the page as completed in the inventory file.
    • Then move to the next page.

  9. Never keep more than one page body in memory at the same time.

  10. After every 10 pages, stop and run a quick verification:

    • check files exist
    • check routes compile
    • check no duplicate slugs
    • check metadata exists
    • check sitemap/robots pattern if applicable

  11. Continue until all pages are completed.

  12. At the end, run final verification and provide summary.

If you hit a Claude API length issue, continue from the inventory file and completed status. Do not restart from scratch.

STRICT BUSINESS SAFETY RULES:

  • Do not remove any existing pages.
  • Do not rename existing URLs.
  • Do not change existing pricing pages unless explicitly asked.
  • Do not break current navigation.
  • Do not delete existing SEO metadata.
  • Do not change design system globally.
  • Do not create thin pages.
  • Do not create duplicate content pages with only city/country swapped.
  • Every page must have unique angle, unique intro, unique FAQs, and unique local/technology relevance.
  • Every page must include strong CTA to WhatsApp/Call: +91 96606 14469.
  • Keep the content focused on .NET job support and real-time project support.
  • Mention interview proxy carefully as “interview support / proxy interview support / live interview support” without making unsafe or unrealistic guarantees.
  • Do not promise job guarantee.
  • Do not claim official Microsoft partnership.
  • Do not use fake testimonials.
  • Do not add fake reviews.
  • Do not invent client names.
  • Do not overuse “best” unnaturally.
  • Use natural SEO, not keyword stuffing.

PROJECT GOAL:

Create a full SEO cluster for:

Modern .NET Azure AI Job Support

Core positioning:

Modern .NET is now .NET 10 + ASP.NET Core + Azure cloud-native + .NET Aspire + AI/ML in .NET + Semantic Kernel + Microsoft Foundry/Azure AI Foundry + RAG + AI Agents + enterprise modernization.

The target audience is developers already working in jobs or preparing for interviews who need:

  • real-time .NET project support
  • .NET job support
  • Azure deployment help
  • debugging help
  • interview support
  • proxy interview support
  • production issue support
  • full-stack .NET help
  • legacy .NET modernization help
  • AI/ML implementation help in .NET

MAIN INTERNAL LINKING FLOW:

Every new page should naturally connect to:

  1. Main parent page: /modern-dotnet-azure-ai-job-support/

  2. .NET Azure page: /dotnet-azure-job-support/

  3. .NET AI/ML page: /dotnet-ai-ml-job-support/

  4. .NET interview page: /dotnet-interview-proxy-support/

  5. Existing site services where relevant:

    • job support service page
    • interview proxy page
    • profile engineering / get interview scheduled page
    • job application / candidate marketing page if exists

Use the actual existing URLs after inspecting the project. Do not guess existing internal URLs if the route exists under a different path. Search the codebase first.

TECHNOLOGY TOPICS THAT MUST BE COVERED ACROSS THE CLUSTER:

Core .NET:

  • .NET 10
  • .NET 9
  • .NET 8 LTS
  • C#
  • ASP.NET Core
  • Web API
  • Minimal APIs
  • MVC
  • Razor Pages
  • Blazor Server
  • Blazor WebAssembly
  • SignalR
  • gRPC
  • Worker Services
  • Background Services
  • Entity Framework Core
  • LINQ
  • Dapper
  • Middleware
  • Dependency Injection
  • Options pattern
  • Configuration
  • Logging
  • Health checks
  • Rate limiting
  • Caching
  • Async/await
  • Performance tuning
  • Memory management
  • Exception handling
  • Clean Architecture
  • Onion Architecture
  • Hexagonal Architecture
  • Domain-Driven Design
  • CQRS
  • MediatR
  • Repository pattern
  • Unit of Work pattern

Azure + .NET:

  • Azure App Service
  • Azure Functions
  • Azure Container Apps
  • Azure Kubernetes Service / AKS
  • Azure API Management
  • Azure Service Bus
  • Azure Event Grid
  • Azure Event Hubs
  • Azure Storage
  • Azure Blob Storage
  • Azure Queue Storage
  • Azure Table Storage
  • Azure SQL Database
  • Azure Cosmos DB
  • Azure Cache for Redis
  • Azure Key Vault
  • Azure Managed Identity
  • Microsoft Entra ID
  • Azure Application Gateway
  • Azure Front Door
  • Azure WAF
  • Azure Virtual Network
  • Private Endpoint
  • Azure Monitor
  • Application Insights
  • Log Analytics
  • Azure DevOps
  • GitHub Actions
  • Azure Pipelines
  • Azure Bicep
  • ARM Templates
  • Terraform
  • Azure Developer CLI

AI/ML in .NET:

  • Microsoft.Extensions.AI
  • Semantic Kernel
  • Azure AI Foundry
  • Microsoft Foundry
  • Azure OpenAI
  • OpenAI SDK for .NET
  • Foundry Models
  • Foundry Agents
  • Azure AI Search
  • RAG in .NET
  • Vector search
  • Embeddings
  • Prompt engineering in .NET
  • Function calling
  • Tool calling
  • AI agents in .NET
  • Agent orchestration
  • Multi-agent workflows
  • Copilot-style enterprise apps
  • Chatbot development in .NET
  • Azure AI Document Intelligence
  • Azure AI Vision
  • Azure AI Language
  • Azure AI Speech
  • Azure AI Translator
  • Azure AI Content Safety
  • Responsible AI
  • Model monitoring
  • Model evaluation
  • Prompt flow
  • LLM tracing
  • Grounded responses
  • Semantic caching
  • Agent memory
  • AI guardrails
  • Model routing
  • ONNX Runtime
  • ML.NET
  • Local AI models with .NET
  • Ollama with .NET
  • Hugging Face with .NET
  • Qdrant
  • Pinecone
  • Weaviate
  • Milvus

Cloud-native .NET:

  • .NET Aspire
  • Aspire AppHost
  • Aspire Dashboard
  • Service discovery
  • Distributed application orchestration
  • Docker
  • Kubernetes
  • AKS
  • Azure Container Apps
  • Dapr
  • YARP reverse proxy
  • API Gateway pattern
  • Microservices architecture
  • Event-driven architecture
  • Saga pattern
  • Outbox pattern
  • Circuit breaker
  • Retry policies
  • Polly
  • Distributed tracing
  • OpenTelemetry
  • Observability
  • Centralized logging
  • Health probes
  • Horizontal scaling
  • Load balancing

Security:

  • OAuth 2.0
  • OpenID Connect
  • JWT
  • Microsoft Entra ID
  • Managed Identity
  • RBAC
  • Claims-based authorization
  • Policy-based authorization
  • API security
  • Azure Key Vault
  • Secrets management
  • Private endpoints
  • Network security groups
  • Application Gateway WAF
  • Azure Front Door WAF
  • mTLS
  • Certificate management
  • Data encryption
  • Secure headers
  • OWASP Top 10
  • Input validation
  • Audit logging
  • Zero Trust architecture
  • AI security
  • Prompt injection protection
  • RAG data leakage prevention
  • PII masking
  • Content filtering

Frontend + .NET:

  • Angular + .NET
  • React + .NET
  • Vue + .NET
  • Blazor
  • TypeScript
  • JavaScript
  • HTML/CSS
  • Bootstrap
  • Tailwind
  • Material UI
  • RxJS
  • NgRx
  • Redux
  • REST API integration
  • SignalR real-time UI
  • SPA deployment on Azure Static Web Apps
  • Frontend/backend authentication flow
  • Micro frontend with .NET backend

Databases:

  • SQL Server
  • Azure SQL
  • PostgreSQL
  • MySQL
  • Cosmos DB
  • MongoDB
  • Redis
  • Elasticsearch
  • Azure AI Search
  • Vector databases
  • Entity Framework Core
  • Dapper
  • Stored procedures
  • Query optimization
  • Indexing
  • Database migration
  • Transaction handling
  • CQRS read/write models
  • Event sourcing
  • Change Data Capture

Testing:

  • xUnit
  • NUnit
  • MSTest
  • Moq
  • FluentAssertions
  • Testcontainers
  • Integration testing
  • Contract testing
  • API testing
  • Postman
  • Playwright
  • Selenium
  • Load testing
  • Azure Load Testing
  • Unit testing
  • Mocking
  • TDD
  • Code coverage
  • Regression testing
  • Security testing

Legacy modernization:

  • .NET Framework to .NET 10 migration
  • .NET Framework 4.8 modernization
  • ASP.NET MVC to ASP.NET Core
  • WebForms to Blazor / Angular / React
  • WCF to gRPC
  • WCF to REST API
  • Windows Service to Worker Service
  • IIS to Azure App Service
  • On-prem to Azure migration
  • Monolith to microservices
  • Legacy authentication to Entra ID
  • Legacy CI/CD to GitHub Actions / Azure DevOps
  • Containerization of old .NET apps
  • AI-assisted code modernization
  • GitHub Copilot app modernization
  • Performance tuning after migration

CREATE THESE PAGES:

PHASE A — MAIN PARENT AND COUNTRY PAGES

  1. Modern .NET Azure AI Job Support URL: /modern-dotnet-azure-ai-job-support/

  2. .NET Job Support in USA URL: /usa-dotnet-job-support/

  3. .NET Job Support in Canada URL: /canada-dotnet-job-support/

  4. .NET Job Support in UK URL: /uk-dotnet-job-support/

  5. .NET Job Support in Ireland URL: /ireland-dotnet-job-support/

  6. .NET Job Support in Germany URL: /germany-dotnet-job-support/

  7. .NET Job Support in Netherlands URL: /netherlands-dotnet-job-support/

  8. .NET Job Support in France URL: /france-dotnet-job-support/

  9. .NET Job Support in Australia URL: /australia-dotnet-job-support/

  10. .NET Job Support in New Zealand URL: /new-zealand-dotnet-job-support/

  11. .NET Job Support in Singapore URL: /singapore-dotnet-job-support/

  12. .NET Job Support in UAE URL: /uae-dotnet-job-support/

  13. .NET Job Support in Saudi Arabia URL: /saudi-arabia-dotnet-job-support/

PHASE B — USA CITY PAGES

  1. .NET Job Support in New York URL: /new-york-dotnet-job-support/

  2. .NET Job Support in Dallas URL: /dallas-dotnet-job-support/

  3. .NET Job Support in Chicago URL: /chicago-dotnet-job-support/

  4. .NET Job Support in Atlanta URL: /atlanta-dotnet-job-support/

  5. .NET Job Support in Houston URL: /houston-dotnet-job-support/

  6. .NET Job Support in Austin URL: /austin-dotnet-job-support/

  7. .NET Job Support in Charlotte URL: /charlotte-dotnet-job-support/

  8. .NET Job Support in Phoenix URL: /phoenix-dotnet-job-support/

  9. .NET Job Support in Seattle URL: /seattle-dotnet-job-support/

  10. .NET Job Support in San Francisco URL: /san-francisco-dotnet-job-support/

  11. .NET Job Support in Los Angeles URL: /los-angeles-dotnet-job-support/

  12. .NET Job Support in Boston URL: /boston-dotnet-job-support/

  13. .NET Job Support in Washington DC URL: /washington-dc-dotnet-job-support/

  14. .NET Job Support in Jersey City URL: /jersey-city-dotnet-job-support/

  15. .NET Job Support in Tampa URL: /tampa-dotnet-job-support/

PHASE C — CANADA, UK, EUROPE, AUSTRALIA CITY PAGES

  1. .NET Job Support in Toronto URL: /toronto-dotnet-job-support/

  2. .NET Job Support in Vancouver URL: /vancouver-dotnet-job-support/

  3. .NET Job Support in Calgary URL: /calgary-dotnet-job-support/

  4. .NET Job Support in London URL: /london-dotnet-job-support/

  5. .NET Job Support in Manchester URL: /manchester-dotnet-job-support/

  6. .NET Job Support in Birmingham URL: /birmingham-dotnet-job-support/

  7. .NET Job Support in Dublin URL: /dublin-dotnet-job-support/

  8. .NET Job Support in Berlin URL: /berlin-dotnet-job-support/

  9. .NET Job Support in Amsterdam URL: /amsterdam-dotnet-job-support/

  10. .NET Job Support in Paris URL: /paris-dotnet-job-support/

  11. .NET Job Support in Sydney URL: /sydney-dotnet-job-support/

  12. .NET Job Support in Melbourne URL: /melbourne-dotnet-job-support/

PHASE D — CORE .NET TECHNOLOGY PAGES

  1. ASP.NET Core Job Support URL: /aspnet-core-job-support/

  2. .NET 10 Job Support URL: /dotnet-10-job-support/

  3. C# Job Support URL: /csharp-job-support/

  4. .NET Web API Job Support URL: /dotnet-web-api-job-support/

  5. ASP.NET Core Minimal API Job Support URL: /aspnet-core-minimal-api-job-support/

  6. Entity Framework Core Job Support URL: /entity-framework-core-job-support/

  7. LINQ Job Support URL: /linq-job-support/

  8. Dapper .NET Job Support URL: /dapper-dotnet-job-support/

  9. Blazor Job Support URL: /blazor-job-support/

  10. SignalR Job Support URL: /signalr-job-support/

  11. gRPC .NET Job Support URL: /grpc-dotnet-job-support/

PHASE E — AZURE + .NET PAGES

  1. .NET Azure Job Support URL: /dotnet-azure-job-support/

  2. Azure App Service .NET Job Support URL: /azure-app-service-dotnet-job-support/

  3. Azure Functions .NET Job Support URL: /azure-functions-dotnet-job-support/

  4. Azure Kubernetes Service .NET Job Support URL: /aks-dotnet-job-support/

  5. Azure Container Apps .NET Job Support URL: /azure-container-apps-dotnet-job-support/

  6. Azure API Management .NET Job Support URL: /azure-api-management-dotnet-job-support/

  7. Azure Service Bus .NET Job Support URL: /azure-service-bus-dotnet-job-support/

  8. Azure Event Grid .NET Job Support URL: /azure-event-grid-dotnet-job-support/

  9. Azure Event Hubs .NET Job Support URL: /azure-event-hubs-dotnet-job-support/

  10. Azure Storage .NET Job Support URL: /azure-storage-dotnet-job-support/

  11. Azure SQL .NET Job Support URL: /azure-sql-dotnet-job-support/

  12. Cosmos DB .NET Job Support URL: /cosmos-db-dotnet-job-support/

  13. Azure Key Vault .NET Job Support URL: /azure-key-vault-dotnet-job-support/

  14. Azure Entra ID .NET Job Support URL: /azure-entra-id-dotnet-job-support/

  15. Azure DevOps .NET Job Support URL: /azure-devops-dotnet-job-support/

PHASE F — .NET AI/ML PAGES

  1. .NET AI/ML Job Support URL: /dotnet-ai-ml-job-support/

  2. Semantic Kernel Job Support URL: /semantic-kernel-job-support/

  3. Microsoft.Extensions.AI Job Support URL: /microsoft-extensions-ai-job-support/

  4. Azure AI Foundry .NET Job Support URL: /azure-ai-foundry-dotnet-job-support/

  5. Azure OpenAI .NET Job Support URL: /azure-openai-dotnet-job-support/

  6. RAG in .NET Job Support URL: /rag-dotnet-job-support/

  7. Vector Search .NET Job Support URL: /vector-search-dotnet-job-support/

  8. AI Agents in .NET Job Support URL: /ai-agents-dotnet-job-support/

  9. Microsoft Agent Framework Job Support URL: /microsoft-agent-framework-job-support/

  10. ML.NET Job Support URL: /mlnet-job-support/

  11. ONNX Runtime .NET Job Support URL: /onnx-runtime-dotnet-job-support/

  12. Azure AI Search .NET Job Support URL: /azure-ai-search-dotnet-job-support/

  13. Azure AI Document Intelligence .NET Job Support URL: /azure-ai-document-intelligence-dotnet-job-support/

  14. OpenAI SDK .NET Job Support URL: /openai-sdk-dotnet-job-support/

  15. Ollama .NET Job Support URL: /ollama-dotnet-job-support/

PHASE G — .NET ASPIRE + CLOUD-NATIVE PAGES

  1. .NET Aspire Job Support URL: /dotnet-aspire-job-support/

  2. .NET Microservices Job Support URL: /dotnet-microservices-job-support/

  3. .NET Cloud Native Job Support URL: /dotnet-cloud-native-job-support/

  4. .NET Kubernetes Job Support URL: /dotnet-kubernetes-job-support/

  5. Dapr .NET Job Support URL: /dapr-dotnet-job-support/

  6. Docker .NET Job Support URL: /docker-dotnet-job-support/

  7. OpenTelemetry .NET Job Support URL: /opentelemetry-dotnet-job-support/

  8. .NET Distributed Tracing Job Support URL: /dotnet-distributed-tracing-job-support/

  9. .NET Resilience Polly Job Support URL: /dotnet-resilience-polly-job-support/

  10. .NET Event Driven Architecture Job Support URL: /dotnet-event-driven-architecture-job-support/

PHASE H — ARCHITECTURE + DESIGN PATTERN PAGES

  1. .NET Clean Architecture Job Support URL: /dotnet-clean-architecture-job-support/

  2. .NET CQRS Job Support URL: /dotnet-cqrs-job-support/

  3. .NET DDD Job Support URL: /dotnet-domain-driven-design-job-support/

  4. .NET Repository Pattern Job Support URL: /dotnet-repository-pattern-job-support/

  5. .NET Hexagonal Architecture Job Support URL: /dotnet-hexagonal-architecture-job-support/

  6. .NET API Design Job Support URL: /dotnet-api-design-job-support/

  7. .NET Performance Tuning Job Support URL: /dotnet-performance-tuning-job-support/

  8. .NET Security Job Support URL: /dotnet-security-job-support/

  9. .NET Authentication Authorization Job Support URL: /dotnet-authentication-authorization-job-support/

  10. .NET Enterprise Architecture Job Support URL: /dotnet-enterprise-architecture-job-support/

PHASE I — FULL STACK .NET PAGES

  1. Full Stack .NET Job Support URL: /full-stack-dotnet-job-support/

  2. Angular .NET Job Support URL: /angular-dotnet-job-support/

  3. React .NET Job Support URL: /react-dotnet-job-support/

  4. Vue .NET Job Support URL: /vue-dotnet-job-support/

  5. Blazor Full Stack Job Support URL: /blazor-full-stack-job-support/

  6. TypeScript .NET Job Support URL: /typescript-dotnet-job-support/

  7. Micro Frontend .NET Job Support URL: /micro-frontend-dotnet-job-support/

  8. SignalR Real-Time App Job Support URL: /signalr-realtime-app-job-support/

PHASE J — DATABASE + DATA PAGES

  1. SQL Server .NET Job Support URL: /sql-server-dotnet-job-support/

  2. PostgreSQL .NET Job Support URL: /postgresql-dotnet-job-support/

  3. MongoDB .NET Job Support URL: /mongodb-dotnet-job-support/

  4. Redis .NET Job Support URL: /redis-dotnet-job-support/

  5. Elasticsearch .NET Job Support URL: /elasticsearch-dotnet-job-support/

  6. .NET Database Migration Job Support URL: /dotnet-database-migration-job-support/

  7. .NET Stored Procedure Job Support URL: /dotnet-stored-procedure-job-support/

  8. .NET Query Optimization Job Support URL: /dotnet-query-optimization-job-support/

PHASE K — LEGACY .NET MODERNIZATION PAGES

  1. .NET Framework to .NET 10 Migration Support URL: /dotnet-framework-to-dotnet-10-migration-support/

  2. ASP.NET MVC to ASP.NET Core Migration Support URL: /aspnet-mvc-to-aspnet-core-migration-support/

  3. WebForms to Blazor Migration Support URL: /webforms-to-blazor-migration-support/

  4. WCF to REST API Migration Support URL: /wcf-to-rest-api-migration-support/

  5. WCF to gRPC Migration Support URL: /wcf-to-grpc-migration-support/

  6. IIS to Azure App Service Migration Support URL: /iis-to-azure-app-service-migration-support/

  7. Monolith to Microservices .NET Support URL: /dotnet-monolith-to-microservices-support/

  8. Legacy .NET Application Modernization Support URL: /legacy-dotnet-application-modernization-support/

PHASE L — INTERVIEW PROXY + INTERVIEW QUESTIONS PAGES

  1. .NET Interview Proxy Support URL: /dotnet-interview-proxy-support/

  2. .NET Proxy Interview Support URL: /dotnet-proxy-interview-support/

  3. ASP.NET Core Interview Proxy Support URL: /aspnet-core-interview-proxy-support/

  4. .NET Azure Interview Proxy Support URL: /dotnet-azure-interview-proxy-support/

  5. .NET AI Interview Proxy Support URL: /dotnet-ai-interview-proxy-support/

  6. .NET Full Stack Interview Proxy Support URL: /dotnet-full-stack-interview-proxy-support/

  7. Senior .NET Developer Interview Questions URL: /interviews/senior-dotnet-developer-interview-questions/

  8. ASP.NET Core Azure Interview Questions URL: /interviews/aspnet-core-azure-interview-questions/

  9. .NET AI ML Interview Questions URL: /interviews/dotnet-ai-ml-interview-questions/

  10. .NET Microservices Interview Questions URL: /interviews/dotnet-microservices-interview-questions/

PAGE CONTENT REQUIREMENTS FOR EVERY PAGE:

Each page must include:

  1. H1 with exact service intent.

  2. Strong opening hook:

    • Candidate is already in job.
    • Candidate is stuck in real-time project.
    • Candidate needs help with tasks, debugging, deployment, architecture, interview rounds, or production support.

  3. Clear service explanation.

  4. “Who this support is for” section.

  5. “Real-time tasks we help with” section.

  6. “Technology stack covered” section.

  7. “Common problems we solve” section.

  8. “How support works” section.

  9. “Why choose Proxy Tech Support” section.

  10. “Interview support connection” section.

  11. CTA section with:

    • WhatsApp / Call: +91 96606 14469
    • Mention remote support available

  12. Internal links to related pages.

  13. FAQ section with at least 5 unique questions.

  14. SEO title.

  15. Meta description between 145–160 characters where possible.

  16. Canonical URL.

  17. Open Graph title and description if project supports it.

  18. Schema markup if project supports schema:

    • Service schema
    • FAQ schema
    • Breadcrumb schema if existing pattern supports it

PAGE LENGTH:

  • Main parent page: 1800–2500 words.
  • Country pages: 1000–1400 words each.
  • City pages: 900–1200 words each.
  • Tech pages: 1200–1800 words each.
  • AI/ML pages: 1400–2000 words each.
  • Interview question pages: 2500+ words with real questions and answers.

CONTENT STYLE:

Write in strong business conversion style.

Tone:

  • human
  • direct
  • practical
  • urgent
  • real-world
  • not academic
  • not generic
  • not robotic

Use buyer-intent language:

  • stuck in .NET project
  • need .NET job support
  • real-time .NET support
  • production issue support
  • Azure deployment help
  • interview round support
  • proxy interview support
  • full-stack .NET task support
  • urgent task help
  • deadline support
  • remote support

Avoid:

  • “In today’s digital world” generic intros
  • overused AI buzzwords without real task examples
  • fake promises
  • copied duplicate content
  • keyword stuffing
  • huge repeated paragraphs across city pages

UNIQUE CONTENT RULE:

Every location page must have unique local angle.

Examples:

USA: Enterprise .NET roles, healthcare, finance, insurance, retail, government contractors, Azure-heavy projects.

Canada: Banking, insurance, healthcare, public sector, Toronto/Vancouver/Calgary enterprise systems.

UK: Fintech, public sector, healthcare/NHS vendor projects, cloud migration, enterprise modernization.

Ireland: Dublin tech hub, Microsoft ecosystem, SaaS, cloud support, EU data/privacy sensitivity.

Germany/Netherlands/France: Enterprise modernization, regulated systems, cloud migration, microservices, Azure security.

Australia/New Zealand: Remote enterprise .NET roles, government/vendor systems, cloud migration, support across time zones.

Singapore/UAE/Saudi: Banking, government digital transformation, cloud modernization, enterprise integrations.

Every tech page must include real project examples.

Examples:

Azure Functions page:

  • timer trigger
  • HTTP trigger
  • queue trigger
  • blob trigger
  • retry failure
  • cold start
  • dependency injection
  • Key Vault
  • Application Insights
  • deployment pipeline

Semantic Kernel page:

  • plugin creation
  • prompt templates
  • tool calling
  • memory
  • RAG integration
  • Azure OpenAI
  • enterprise chatbot
  • agent workflow

.NET Aspire page:

  • AppHost setup
  • service discovery
  • dashboard
  • local orchestration
  • Redis/Postgres integration
  • container deployment
  • observability

ASP.NET Core page:

  • middleware
  • DI
  • filters
  • model binding
  • validation
  • authentication
  • authorization
  • API performance
  • production debugging

INTERNAL LINKING REQUIREMENTS:

For each page, add a related support section.

For parent page: Link to all major category pages:

  • country pages
  • core .NET pages
  • Azure pages
  • AI pages
  • interview pages
  • full-stack pages
  • modernization pages

For country pages: Link to:

  • parent page
  • .NET Azure job support
  • .NET AI/ML job support
  • ASP.NET Core job support
  • .NET interview proxy support
  • relevant city pages

For city pages: Link to:

  • related country page
  • parent page
  • .NET Azure page
  • ASP.NET Core page
  • interview proxy page

For Azure pages: Link to:

  • .NET Azure Job Support
  • parent page
  • Azure DevOps page
  • Azure Key Vault page
  • Azure Functions or App Service page
  • .NET interview proxy page

For AI pages: Link to:

  • .NET AI/ML Job Support
  • Semantic Kernel
  • Azure AI Foundry
  • Azure OpenAI
  • RAG in .NET
  • AI Agents in .NET
  • parent page

For interview pages: Link to:

  • parent page
  • ASP.NET Core Job Support
  • .NET Azure Job Support
  • .NET AI/ML Job Support
  • Full Stack .NET Job Support

NAVIGATION / DISCOVERY:

Add one new section on home page only if safe and minimal:

Title: Modern .NET, Azure & AI Job Support

Text: Get real-time .NET job support for ASP.NET Core, Azure, .NET 10, Semantic Kernel, Azure AI Foundry, microservices, full-stack .NET, and production project issues.

CTA: Explore .NET Job Support

Link: /modern-dotnet-azure-ai-job-support/

Do not redesign home page. Add only a safe small section following existing component style.

Add links from existing relevant pages where safe:

  • Job Support page
  • Interview Proxy page
  • Technologies page
  • Blog/interviews index if exists
  • Main services index if exists

Again: do not rewrite existing pages. Only add small internal link sections.

SEO REQUIREMENTS:

For every page:

  • Unique H1
  • Unique SEO title
  • Unique meta description
  • Unique canonical
  • Open Graph metadata if supported
  • FAQ schema
  • Breadcrumb schema if existing pattern supports it
  • Service schema if existing pattern supports it
  • Add to sitemap if sitemap is manually maintained
  • If sitemap is auto-generated, verify route is included

Suggested SEO title format: [Page Topic] | Real-Time .NET Job Support

Examples: Azure Functions .NET Job Support | Real-Time Project Help Semantic Kernel Job Support | .NET AI Agent Project Support .NET Job Support in USA | ASP.NET Core, Azure & AI Help

Suggested meta description format: Get real-time [topic] support for .NET developers working on ASP.NET Core, Azure, AI/ML, debugging, deployment, and interview tasks.

FAQ QUESTIONS EXAMPLES:

Use unique FAQs per page, but these patterns can be adapted:

  1. Do you provide real-time .NET job support?
  2. Can you help with ASP.NET Core and Azure project tasks?
  3. Do you support .NET AI/ML and Semantic Kernel projects?
  4. Can you help with urgent production issues?
  5. Do you provide .NET interview proxy support?
  6. Can you help with legacy .NET modernization?
  7. Do you support Angular .NET or React .NET full-stack tasks?
  8. Can you help with Azure deployment and CI/CD issues?
  9. Do you provide support for candidates in USA/Canada/UK/etc.?
  10. How do I contact you for .NET job support?

QUALITY CHECKS:

After every 10 pages:

  • List generated files.
  • Confirm each route exists.
  • Confirm metadata exists.
  • Confirm internal links are valid.
  • Confirm no duplicate H1.
  • Confirm no duplicate meta description.
  • Confirm no build errors.
  • Update inventory status.

FINAL CHECK:

After all pages:

  1. Run build command if available:

    • npm run build
    • pnpm build
    • yarn build Use the correct one based on project.

  2. Run lint if available.

  3. Check sitemap.

  4. Check route list.

  5. Check no broken internal links where possible.

  6. Provide final report:

    • total pages created
    • files created
    • existing files touched
    • sitemap updated or auto-generated
    • nav/home additions
    • build status
    • errors if any

IMPORTANT PAGE INVENTORY FORMAT:

Create /content-plans/modern-dotnet-page-inventory.json with this structure:

[ { "id": 1, "phase": "A", "title": "Modern .NET Azure AI Job Support", "slug": "modern-dotnet-azure-ai-job-support", "url": "/modern-dotnet-azure-ai-job-support/", "type": "parent", "primaryKeyword": "modern .NET Azure AI job support", "secondaryKeywords": [ ".NET job support", ".NET Azure job support", ".NET AI/ML job support", "ASP.NET Core job support", ".NET interview proxy" ], "status": "pending", "filePath": "", "metaTitle": "", "metaDescription": "", "internalLinks": [] } ]

For each page:

  • status starts as pending
  • update to completed after physical file is created and saved
  • add filePath after file creation
  • add actual metaTitle/metaDescription
  • add actual internalLinks used

IMPORTANT: continue using this inventory file as the single source of truth. Do not rely on memory for what has been completed.

CONTENT GENERATION METHOD:

For each page, use this exact mini workflow:

Step 1: Read page object from inventory.

Step 2: Create page outline only for that one page.

Step 3: Generate content only for that one page.

Step 4: Write the content to the physical page file.

Step 5: Save file.

Step 6: Update inventory status to completed.

Step 7: Move to next page.

Do not batch generate multiple full pages together.

Do not keep outlines for all pages in memory.

Do not generate all FAQs together.

Do not generate all schemas together.

Each page must be self-contained and saved immediately.

START NOW:

First inspect the project structure.

Then create the planning folder and inventory file.

Then begin with page 1: /modern-dotnet-azure-ai-job-support/

Proceed page by page until all 135 pages are created, verified, internally linked, and included in sitemap/navigation where appropriate.