Almost always, the tutorial is right and it is simply older than your WordPress. In one year the admin has moved through two major releases and several point releases, and a guide written before either one describes a screen that no longer exists. The fix is not to hunt for a better tutorial. It is to find out which version you are running, work out which release the guide was written against, and read the gap between them.
Verified against WordPress 7.1 "Mary Lou", released 19 August 2026. Last verified 26 August 2026. Sources are WordPress's own: the 7.0 and 7.1 version pages on WordPress.org, the WordPress.org releases archive, and the WordPress 7.1 Field Guide on make.wordpress.org. Admin screens change between releases, so check which version you are running before assuming a step you read somewhere is wrong.
Step one: find out which WordPress you are actually running
You cannot judge a tutorial until you know what you are comparing it to, and this takes about ten seconds.
The version number is shown in the admin itself, in the At a Glance panel on the Dashboard and in the footer of admin screens, and the Dashboard's Updates screen tells you both what you are on and what is available. If you have never looked, look now and write it down, because every other decision in this article depends on it.
Then check whether you are behind. WordPress.org publishes a releases archive listing every version and the date it shipped. If your number is not the current one, a good part of the mismatch you are seeing is explained before you read another word.
Being behind is a decision, not an accident, and it is a decision worth making deliberately rather than by default. But it does mean the newest tutorials will describe screens you do not have yet, which is the same problem in the opposite direction.
The two releases that produced most of the confusion
Two dates explain the majority of what people are running into right now.
WordPress 7.0 "Armstrong" was released on 20 May 2026. It is the release that changed the shape of the everyday screens, and it is the boundary that makes older tutorials look wrong.
WordPress 7.1 "Mary Lou" was released on 19 August 2026, three months later, and it changed a further set of things on top. Its Field Guide, published on 5 August 2026, groups the changes under Media, Accessibility, the Abilities API, Global Styles, the SVG Icon API, DataViews and the related APIs, the Editor, the Design System, the Persistent Admin Bar and External Libraries.
So there are now three populations of tutorial in circulation: written before May 2026, written between May and August 2026, and written after August 2026. All three are on the same results page, usually with no date visible, and what actually landed in 7.1 is the line that separates the last two.
Step two: read the tutorial for its version, not its date
A publication date is weak evidence, because pages get republished with a fresh date and no change to the content. There is better evidence inside the page.
Look at what the screenshots show. A Posts screen that is a plain table with the old Screen Options tab in the corner is pre-7.0. A Posts screen with a filterable view and layout choices is 7.0 or later.
Look at what the article names. If it talks about the Customizer as the main way to change the site's appearance, it is describing an older setup than most sites now run. If it names DataViews, a command palette, or the Connectors screen, it is at least 7.0.
Then decide what to do with it. Most older tutorials are still correct about the goal and only wrong about the route: the setting still exists, it is reached differently. Those are worth keeping. Tutorials that depend on a screen having a particular shape, and step-by-step instructions with exact pixel positions, are the ones to abandon. When you need a route rather than a concept, a walkthrough written against the admin that exists now is a shorter path than translating an old one.
Four reasons your screen differs, and only one is the version
Version explains most of it. It does not explain all of it, and the other three are worth ruling out before you conclude your install is broken.
Your core version, as above.
Your theme. A block theme gives you the Site Editor as the place appearance is edited. A classic theme does not, and gives you the Customizer and menu screens instead. Two sites on the identical WordPress version will show meaningfully different Appearance sections for this reason alone, and a tutorial that assumes one will look wrong on the other.
Your plugins. Plugins add menu items, add whole screens, and in some cases restyle or hide parts of the admin outright. A security or admin-customization plugin can remove exactly the menu entry a tutorial tells you to click.
Your user role. WordPress shows each user only the screens their role permits. If a tutorial says to go to Settings or Plugins and there is no such menu, the likeliest explanation is not a missing feature but an account that is not an administrator.
The most common mis-dating on the web right now
There is a specific error worth knowing about, because it is widespread and it will send you looking for something that is not there.
A large amount of content attributes the Media Library changes to WordPress 7.0. They are 7.1. The 7.0 Field Guide has no Media Library section at all; the media work, including client-side image processing in the browser and infinite scrolling enabled by default in the Media Library grid, is documented in the 7.1 Field Guide, published 5 August 2026.
The practical consequence: if you are on 7.0.x and a guide describes Media Library behavior you cannot find, you are not missing a setting. You are on the release before the one that changed it. The media changes that a lot of pages date to the wrong release are the clearest current example of a whole cluster of pages copying one another's mistake.
The thing that is genuinely absent, and why that matters here
Not every difference between a tutorial and your screen is a version gap. Sometimes the feature never shipped.
Real-time collaboration is the standing example. It is not enabled in 7.1. It has been discussed publicly for long enough that plenty of articles describe it as if it were available, and a reader who goes hunting for it in their own admin will not find it, on any current version.
So the third possible answer, after "you are behind" and "you are ahead", is "it does not exist." That one is only settleable from the release record, which is why the record beats the tutorial every time.
The release record is public, and it is the only tie-breaker
When two pages disagree about what your WordPress does, neither of them is evidence. The project's own documents are.
Three things are published for every release: the version page on WordPress.org, the release announcement, and the Field Guide on make.wordpress.org that collects the developer notes for everything that changed. The Field Guide is written for developers and it is longer than you want, but it is searchable and it is definitive, and finding out whether a feature exists in your version usually takes one search inside one page.
That is a skill worth having rather than a chore, because it turns the version question from a recurring frustration into a thirty-second check, and reading a release note yourself is the whole of it.
What to do with the tutorial you were reading
If the goal still exists and only the route changed, keep the tutorial for the goal and find the route in the current admin. This is most of them.
If the tutorial is telling you to click something that no longer exists at all, check the Field Guide for the release that removed or replaced it before assuming it is gone, because features are more often moved than deleted.
If the tutorial describes something your version does not have yet, the question becomes whether to update, which is a separate decision with its own checklist and is not something to do mid-task because a guide looked unfamiliar.
And if the screen is missing entirely rather than just different, check your role and your active plugins before anything else. That is the fastest of the four checks and it is the one people skip.
FAQ
Why does my WordPress dashboard look different from the tutorials?
Most likely because the tutorial predates WordPress 7.0, released 20 May 2026, which changed the shape of the everyday screens. Your theme, your plugins and your user role account for most of what version does not explain.
How do I check which version of WordPress I am running?
The version appears in the At a Glance panel on the Dashboard and in the admin footer, and the Dashboard's Updates screen shows both your version and the latest available.
Is an old WordPress tutorial still useful?
Usually yes for the goal and no for the route. Settings tend to survive redesigns and change location, so an older guide is often right about what you are trying to do and wrong about where you click.
Why can I not see the Plugins or Settings menu?
WordPress shows each user only what their role allows. An account that is not an administrator will not see those menus, and that is a permissions result rather than a missing feature.
Where can I check what a WordPress release actually changed?
The version page on WordPress.org, the release announcement, and that release's Field Guide on make.wordpress.org. The Field Guide is the one that lists everything, and it is searchable.
