What users should find on this page

• Developer profile and the countries or cities in which documented projects are located.
• Residential, mixed-use, office, hospitality, retail, urban district or regeneration projects.
• Connections to architecture and design teams credited on each project.
• WAIDE Development recognition where applicable.
• Related city, country and sector pages that help users continue discovery.

How WAIDE organizes the information

WAIDE should treat every important item on this page as an entity with its own permanent URL. A project can be connected to a studio, one or more credited people, a city, a country, a discipline, a category, a project status and an award year. These relationships allow users to move naturally through the platform and also reduce the need to create repetitive standalone pages for every possible keyword combination. For search engines, this creates a clearer information architecture. For AI discovery systems, it provides explicit relationships that are easier to extract and interpret.

Quality and inclusion principles

Directory inclusion should be based on real project participation, verified professional information, WAIDE submissions, awards, editorial review or another documented relationship with the platform. Empty profiles, duplicated entities and automatically generated pages without useful information should not be indexed.

Recommended page structure

• Short answer-first introduction explaining the page and its scope.
• Featured or recently added entities with meaningful captions.
• Filter controls for the most useful dimensions, such as category, location, year or project status.
• Entity cards linking to canonical project, studio, person or developer profiles.
• Context section explaining how WAIDE classifies the discipline or project type.
• Related countries, cities, categories and editorial stories.
• Submission or participation call to action where relevant.

Internal linking

This page should link to the relevant WAIDE award category, the main Projects or People hub, country and city hubs, related editorial stories, and individual entity pages. Individual entities should link back to this collection only when the relationship is meaningful. Avoid sitewide blocks containing hundreds of repetitive links.

Indexation and technical SEO

Use a clean canonical URL and keep sorting parameters, empty filters and low-value combinations out of the index. Add the page to the relevant XML sitemap only after it contains substantive content. Pagination or load-more behaviour should preserve crawlable links to important entity pages. Titles and descriptions can be updated over time, but the canonical URL should remain stable whenever the underlying search intent is evergreen.