ARQUITECTURA WEB: Cómo organizar bien las páginas de tu Web | CURSO SEO #8

Main ideas and lessons (web architecture for SEO)

1) What “web architecture” is (core definition)

• Web architecture = Information Architecture + Technical Architecture
• Its goal is to define how the website is structured so that:
  • Users can access information quickly and clearly
  • Bots (e.g., Googlebot) can crawl and index content efficiently

2) Two components that build web architecture

A. Information architecture (what it consists of)

• Organizing, structuring, and labeling the website’s important elements/content
• Purpose:
  • Make content understandable
  • Make content comprehensible
  • Make content findable (“most importantly, findable”)
• Example (coffee-themed, conceptual):
  • Organize content like coffee makers by type, by brand, and related attributes
  • Create a hierarchical structure that later becomes the site’s structure

B. Technical architecture (what it consists of)

• Translating the information architecture into the real website
• Includes technical elements such as:
  • Crawling behavior (how bots discover pages)
  • Click depth (how many clicks away content is)
  • Prioritization (how to rank importance across many URLs/pages)

3) Purpose of web architecture (what it’s for)

• For users:
  • Improve navigability so users can find content easily
• For bots (Googlebot):
  • Improve the crawl → index → classify process
  • If Googlebot finds content easily/quickly, it’s easier to index and classify
• Also supports:
  • Prioritizing pages/URLs when there is lots of content
  • Clarifying that not all URLs are equally important—you must decide which should matter most

4) Inputs needed before building architecture

The lesson emphasizes that you should:

• Do keyword research (“keyword reset” / keyword study)
• Perform SEO competitor analysis
• Use the results to inform:
  • The site structure (information architecture)
  • The technical setup (technical architecture)
• Also consider structural elements typically tied to implementation:
  • Menus, footers, sidebars
  • What changes when transferring the plan to the website

---

Methodology / practical instructions presented

A) Step-by-step building approach (conceptual workflow)

1. Start with information architecture
   • Draw the site’s hierarchical organization:
     • categories/types
     • brands
     • features
     • blogs
     • other pages
2. Define technical architecture
   • Translate the hierarchy into the real website structure:
     • ensure crawlability
     • decide click distance (depth)
     • plan prioritization across pages
3. Prioritize URLs
   • When many pages exist, assign relative importance so resources are used effectively
4. Validate with navigation principles
   • Ensure both:
     • downward navigation
     • upward context navigation

B) Navigation principles (two types)

• Descending navigation
  • Usually via menus and linking modules
  • Meaning: a user clicks from a menu/module down into categories/sections
• Ascending navigation
  • Uses breadcrumbs
  • Meaning: the user sees “you are here” context (e.g., Home → Section → Current page)
  • Clicking breadcrumbs helps users navigate up to higher-level categories/pages

C) “Web architecture types” guidance

• There is no single perfect web architecture for all projects.
• Instead:
  • Adapt the architecture to project needs and constraints
  • Potentially redefine the information architecture
  • Then translate it to the website with appropriate prioritization
• Even if sites seem similar, each one differs in:
  • needs
  • peculiarities
  • prioritization strategy

D) Depth rule (“three-click depth”)

• Presented as a general standard:
  • try to keep important info within ~3 clicks
• But it’s not always applicable:
  • larger sites, authority, and context may require more depth
• The intent is to ensure:
  • efficient Googlebot crawling and indexing
  • bots don’t “get lost”

---

Computer demonstration: using mind-mapping tools to plan architecture

Tools mentioned/used

• Primary tool demonstrated: XMind (referred to as “xmain” in subtitles)
• Other tools mentioned as commonly used:
  • FreeMind
  • Draw.io (“drum.yo” pronounced in subtitles)

Demonstration workflow (as shown)

• Open the tool and create a new blank map
• Center the domain (example shown with a coffee shop domain)
• Insert main top-level nodes, such as:
  • types/categories
  • brands
  • features
  • blogs
  • other pages
• Use earlier outputs as inputs:
  • keyword study (keyword research)
  • competitor search engine analysis
• Build category nodes under “types,” including example URLs like:
  • espresso machines
  • Italian coffee makers
  • automatic coffee machines
  • capsule coffee machines
  • electric coffee machines
  • coffee machines with grinders

How URL/page metadata is captured in the map

For each page/category node, the map can include:

• the keyword used for the URL (or the URL itself)
• title
• description
• the URL path/structure
• links to related pages connected from the homepage (internal linking plan)

Prioritization system in the map

• Nodes/pages can be assigned a priority level (e.g., priority 1 vs priority 2)
• The map supports filtering/viewing:
  • show only priority 1 items
  • fold/hide instructions and content for easier review

Numbering/depth explanation (important clarification)

The video clarifies that numbering can be used in two ways:

• As priority levels (which URLs matter most)
• As depth levels (how many clicks away a URL is)

It specifically connects numbering to depth:

• Level 1, Level 2, Level 3 correspond to click distance
• The explanation also allows for multiple URLs at each depth level (up to 3 levels described as common)

The architecture shown in the description is said to already include completed numbering and depth visualization.

---

Speaker(s) / sources featured

Speaker / source

• Villanueva (mentioned repeatedly as the presenter/teacher)
• YouTube video series / course name: “Desire for Beginners” (free course referenced as the source of the lesson)