Permalink structure in Wordpress - Step-by-Step Execution

Concept Flow - Permalink structure

User sets permalink format

↓

WordPress saves permalink setting

↓

User visits a URL

↓

WordPress parses URL

↓

Match URL to content type

↓

Load and display content

↓

Show page with friendly URL

This flow shows how WordPress uses the permalink structure set by the user to parse URLs and display the correct content with friendly URLs.

Execution Sample

Wordpress

1. User sets permalink to '/%postname%/'
2. User visits 'example.com/my-post/'
3. WordPress parses 'my-post'
4. Finds post with slug 'my-post'
5. Displays the post content

This example shows how a permalink with post name is used to find and display the correct post.

Execution Table

Step	Action	Input/State	Result/Output
1	Set permalink structure	User selects '/%postname%/'	Permalink saved in settings
2	User visits URL	URL: example.com/my-post/	URL received by WordPress
3	Parse URL	Extract 'my-post' from URL	Slug identified as 'my-post'
4	Query content	Search post with slug 'my-post'	Post found in database
5	Display content	Post data loaded	Post page shown with friendly URL
6	End	All steps done	Page rendered successfully

💡 Execution stops after content is displayed for the matched permalink URL.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
permalink_structure	default	/%postname%/	/%postname%/	/%postname%/	/%postname%/
requested_url	none	example.com/my-post/	example.com/my-post/	example.com/my-post/	example.com/my-post/
slug	none	none	my-post	my-post	my-post
post_found	false	false	false	true	true

Key Moments - 2 Insights

Why does WordPress need to parse the URL after setting the permalink?

Because the permalink structure defines how URLs look, WordPress must parse the URL to find the correct content. See execution_table step 3 where the slug is extracted from the URL.

What happens if the slug in the URL does not match any post?

WordPress will not find content and usually shows a 404 error. This is implied after step 4 if 'post_found' is false in variable_tracker.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. What is the slug extracted from the URL?

A "postname"

B "my-post"

C "example.com"

D "/%postname%/"

💡 Hint

Check the 'Result/Output' column at step 3 in the execution_table.

At which step does WordPress find the post in the database?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'Action' and 'Result/Output' columns in the execution_table.

If the permalink structure changed to '/%year%/%postname%/', what would change in the variable_tracker?

A The slug variable would include the year

B The requested_url would no longer be 'example.com/my-post/'

C The permalink_structure variable would update to '/%year%/%postname%/'

D The post_found variable would become false

💡 Hint

Check the 'permalink_structure' row in variable_tracker for changes.

Concept Snapshot

Permalink structure in WordPress defines how URLs look.
User sets a format like '/%postname%/'.
WordPress parses URLs to find content by matching parts like post slug.
This makes URLs user-friendly and SEO-friendly.
Changing permalink affects URL parsing and content lookup.

Full Transcript

In WordPress, the permalink structure controls how URLs appear for posts and pages. When a user sets a permalink format, WordPress saves this setting. When someone visits a URL, WordPress parses the URL according to the permalink structure to extract key parts like the post slug. It then searches the database for content matching that slug. If found, WordPress loads and displays the content with the friendly URL. This process helps make URLs readable and meaningful. If the URL does not match any content, WordPress shows a 404 error. Changing the permalink structure changes how URLs are parsed and matched to content.