killdisk.com

If you're new to Ahrefs and want to run your first SEO audit, the fastest path is: open Site Explorer, enter your target URL, review the Overview for a health snapshot, then dig into Organic Keywords, Top Pages, and Site Audit to find specific problems. From there, build a short prioritized to-do list instead of trying to fix everything at once.

This tutorial walks through that workflow using a realistic starting scenario, explains what the numbers mean, and shows how to turn findings into actions.

Before You Start: Pick a Narrow Scope

A common beginner mistake is auditing an entire large website on day one. The reports become overwhelming, and you can't tell which issues matter.

Instead, choose one of these starting points:

• A single important page (your homepage or a key product/service page)
• A small site (under ~50 pages, e.g., a personal blog or small business site)
• One section of a bigger site (e.g., /blog/)

For this tutorial, assume you're auditing a small business site with about 30 pages. The same steps scale up later.

You'll need an Ahrefs account to follow along. Ahrefs offers paid plans, and pricing and feature limits change over time, so check the current Pricing page for what's included in each tier before committing.

Step 1: Enter Your Target in Site Explorer

Site Explorer is Ahrefs' core tool for analyzing any website or URL.

1. Open Site Explorer from the top navigation.
2. In the search box, paste your domain (e.g., example.com).
3. Choose the Exact URL or Domain mode depending on scope. For a full-site view, use Domain or Prefix; for a single page, use Exact URL.
4. Press Enter.

You'll land on the Overview report. Don't try to absorb everything — focus on four numbers first.

Reading the Overview Snapshot

Important caveat: Ahrefs' traffic and keyword numbers are estimates based on its own data. They won't match Google Search Console or your analytics exactly. Treat them as directional, not absolute.

Step 2: See What You Already Rank For

Go to Organic Keywords in the left sidebar. This shows queries where your site appears in search results.

Sort by Traffic (descending) to see which pages bring the most estimated visitors. Then look for:

• Keywords ranking in positions 4–15 — these are often the easiest wins. A small content or on-page improvement can push them onto page one.
• Keywords with high volume but low position — potential opportunities if the topic is relevant.
• Irrelevant keywords — if you rank for something off-topic, it may signal thin or mismatched content.

Write down 5–10 of the position 4–15 keywords. These become your first optimization targets.

Step 3: Find Your Best and Weakest Pages

Open Top Pages. This ranks your URLs by estimated organic traffic.

Look for two things:

1. Your top performers — understand what topics and formats work. Can you create more content like this?
2. Pages with traffic but poor rankings — these may need on-page fixes (title, headings, internal links).

If a page gets zero traffic and targets a topic you care about, it's a candidate for a rewrite or consolidation.

Step 4: Run a Technical Site Audit

Now move to Site Audit. This crawls your site and flags technical and on-page issues.

1. Click Site Audit → New project.
2. Enter your domain and set crawl settings (default is usually fine for a small site).
3. Start the crawl and wait for it to finish.

Once complete, you'll see a Health Score and a list of issues grouped by category.

Which Issues to Fix First

Not all issues are equal. Prioritize in this order:

Ignore low-impact warnings (like minor meta description length) until the big items are handled.

Step 5: Turn Findings Into a To-Do List

You now have raw data. Convert it into a short, actionable list. Example:

1. Fix 3 broken links found in Site Audit.
2. Rewrite title tags on 5 pages with duplicate titles.
3. Improve 4 pages ranking in positions 6–12 by adding missing subtopics and internal links.
4. Remove or update 2 thin pages with no traffic.

Keep the list to 5–10 items max for your first audit. Finishing a short list beats starting a long one.

Common Beginner Mistakes

• Chasing every red flag. Site Audit flags many minor issues. Fix what affects rankings and users first.
• Trusting estimates as exact numbers. Ahrefs data is modeled, not measured from your analytics.
• Auditing a huge site too early. Start small to learn the interface.
• Ignoring search intent. A page can be technically perfect but still fail if it doesn't match what searchers want.
• Forgetting to re-crawl. After fixes, run Site Audit again to confirm improvements.

Where to Go Next

Once your first audit is done:

• Compare with competitors using Site Explorer's Competing Domains and Content Gap reports.
• Track keyword rankings over time with Rank Tracker.
• Explore backlink opportunities in the Backlinks and Link Intersect reports.
• Set up recurring Site Audit crawls so new issues surface automatically.

Your first audit isn't about perfection — it's about building a repeatable habit: enter a target, read the key reports, pick the highest-impact fixes, and act. Do that once a month and your site's health compounds.

DOS (Disk Operating System) was the command-line operating system that most IBM-compatible PCs ran before Windows became the dominant environment, and it's the platform nearly every classic PC game from the 1980s and early-to-mid 1990s was built for. Because modern 64-bit Windows, macOS, and Linux can't run those games natively, you play them through an emulator such as DOSBox, or through a site that packages the emulator and game together so it launches with a click. This article explains what DOS actually was, why emulation is necessary, and how to get a DOS game running — including the sound, speed, and fullscreen problems that trip most people up.

What DOS actually was

DOS is not a single product but a family of operating systems. The version that mattered for gaming was MS-DOS (Microsoft) and its close relative PC DOS (IBM), with compatible clones like DR-DOS and FreeDOS filling out the field. Key traits:

• Command-line interface. You typed commands at a prompt (C:\>) rather than clicking icons. Games typically launched by typing an executable name, e.g. PRINCE or DOOM.
• Real-mode memory model. Early DOS gave programs direct access to hardware and to a limited pool of conventional memory (640 KB), which is why so many games shipped with memory-configuration instructions for CONFIG.SYS and AUTOEXEC.BAT.
• Direct hardware access. Games talked straight to the sound card, graphics adapter, and input devices. That's what made them fast on period hardware — and what makes them fragile on modern machines, where the operating system mediates all hardware access.
• No multitasking. One program ran at a time. Later versions added limited memory management, but the model stayed fundamentally single-tasking.

Windows 3.1 and Windows 95 could run on top of DOS, and many games of that era shipped as DOS executables launched from within Windows. That's why a preservation project like Zomb's Lair lists DOS alongside Windows 3.1 and Amiga as separate platforms — they're genuinely different targets requiring different handling.

Why you need an emulator on a modern PC

A DOS game expects to own the machine: it writes directly to video memory, programs the sound chip, and reads the keyboard hardware. A modern OS forbids all of that. Three practical consequences:

1. 64-bit Windows cannot run DOS programs at all. The NTVDM (NT Virtual DOS Machine) that provided DOS support was dropped from 64-bit builds. On 32-bit Windows it still exists, but it's unreliable for games.
2. Timing breaks. DOS games often tied game speed to CPU clock speed. On a multi-gigahertz processor, a game designed for a 33 MHz 486 may run absurdly fast or refuse to start.
3. Sound hardware is gone. The Sound Blaster, AdLib, and Gravis Ultrasound cards these games target don't exist in modern machines, and the games don't know how to use what replaced them.

DOSBox solves all three by emulating a complete DOS PC — CPU, video, sound card, and all — inside a window. It's the standard tool, it's free and open source, and it runs on Windows, macOS, and Linux.

Where to get DOS games

You have two broad routes, and they differ mainly in how much setup you do yourself.

Preservation and curation projects occupy the second category. Zomb's Lair, for example, describes itself as "a passion project dedicated to bringing old classics to a modern audience, while eliminating all of the hurdles that that normally entails," and organizes its catalog by platform (DOS, Amiga, Windows 3.1) and by genre (Adventure, RPG). The value of that kind of packaging is precisely the configuration work — memory settings, sound setup, and speed calibration — done for you.

A note on the legal side, since it affects which route you choose: much of this material is abandonware — old commercial software whose publisher has stopped selling or supporting it. Abandonware is a community norm, not a legal category, and rights holders can and do re-release games commercially. Where a game is currently sold (on GOG, Steam, or elsewhere), buying it is both the safer and usually the easier path, since those storefronts ship pre-configured DOSBox builds too.

Running a DOS game: the basic steps

If you're configuring DOSBox yourself, the workflow is the same for almost every game.

1. Install DOSBox for your platform and note where you put your game folder. Keep paths short and free of spaces — C:\DOS\GAMES\GAMENAME rather than a deep folder with spaces in the name. DOS itself had no concept of long filenames.
2. Mount a drive. At the DOSBox prompt, MOUNT C points an emulated drive letter at a real folder. The expected result is a confirmation message; if you get an error, the path is wrong.
3. Switch to that drive and change into the game directory.
4. Run the game's setup utility first if it has one (commonly SETUP.EXE, INSTALL.EXE, or SOUNDSET.EXE). This is where you tell the game which sound card to use — pick Sound Blaster or Sound Blaster 16 with the default port and IRQ values, which is what DOSBox emulates.
5. Launch the game by typing its executable name.
6. Adjust speed if needed. DOSBox's cycle count controls how fast the emulated CPU runs; raising it speeds a sluggish game up, lowering it slows a too-fast one down.

If you're using a pre-packaged release, steps 1–4 are already done. You launch a shortcut and the emulator starts with the right drive, sound, and speed settings.

Troubleshooting the usual problems

No sound, or sound only in some places. The game's own setup utility is almost always the culprit — it's still configured for a card DOSBox doesn't emulate. Re-run setup and select Sound Blaster. If the game predates sound-card setup utilities, it may only support PC speaker audio, which DOSBox emulates but which sounds thin by design.

Game runs too fast or too slow. This is the cycle setting. Games from the late 80s and early 90s are the most sensitive. Some front-ends let you bind hotkeys to raise and lower cycles while the game runs, which is the fastest way to find a stable value.

Fullscreen looks stretched or has black bars. DOS games ran at fixed resolutions like 320×200, which don't match a modern monitor's aspect ratio. Stretching fills the screen but distorts the image; leaving it unstretched preserves the original proportions. There's no correct answer — pick based on whether you prefer accuracy or a filled screen.

The game can't find enough memory. Classic DOS memory errors come from the 640 KB conventional-memory limit. DOSBox handles most of this automatically, but games with unusual requirements may need specific memory settings in the emulator's configuration file.

Keyboard or mouse doesn't respond correctly. DOSBox captures input when the game window is focused; releasing the capture (usually with a hotkey) returns control to your desktop. If a game needs a joystick, it has to be configured both in DOSBox and in the game's own setup.

What to take away

DOS was the command-line, single-tasking, hardware-direct operating system that defined PC gaming for roughly a decade, and its design is exactly why those games don't run on a modern machine without help. DOSBox emulates the whole environment; packaging projects remove the configuration burden on top of that. If you want to play rather than configure, start with a pre-packaged release and treat the game's own setup utility as the first thing to check whenever sound or speed misbehaves.