SearchBulb

Category: SEO

  • Types of Schema Markup: The Complete Guide

    Types of Schema Markup: The Complete Guide

    If you’ve searched “types of schema markup,” you’ve probably landed on a list of 20-something items and closed the tab more confused than when you opened it. Most of those types don’t apply to your site at all.

    This guide is different. It covers the schema types that actually show up on real websites, grouped by what they’re for, so you can find yours in under a minute. Then it covers something most schema guides skip entirely: how to connect your schema into one consistent structure instead of a pile of disconnected code blocks.

    Quick summary: What to actually know:

    • Schema.org lists 797 types and 1,453 properties, but most sites only ever need 10 to 15 of them.
    • Schema isn’t a direct Google ranking factor, but it drives rich results, which drive clicks, which do affect rankings indirectly.
    • The types you pick should match what’s actually visible on the page, nothing hidden or invented.
    • A solid schema setup connects an Organization and a WebPage entity as a foundation, then layers page-specific types on top.

    What Is Schema Markup?

    Schema markup is structured code you add to a page that tells search engines exactly what the content is, not just what it says. Instead of Google guessing that a page is “probably about a recipe” from the text, schema states it directly: this is a Recipe, here’s the cook time, here are the ingredients.

    It’s written using a shared vocabulary from schema.org, a project Google, Microsoft, Yahoo, and Yandex jointly started in 2011 to standardize how structured data works across the web. The most common format today is JSON-LD, a small script tag that sits in your page’s code without changing anything visitors actually see.

    When it works, schema is why some search results show star ratings, prices, event dates, or FAQ dropdowns instead of a plain blue link.

    Does Schema Markup Actually Help Rankings?

    Not directly, and it’s worth being upfront about that. Google has said structured data isn’t a ranking factor on its own.

    What it does do is make your result more likely to earn a rich snippet, and rich snippets get more clicks. Higher click-through rates are one of the signals that can indirectly support your rankings over time. Schema also gives search engines and AI tools a clearer, more literal read of your content, which matters more now that AI Overviews and other answer engines are pulling directly from structured, well-labeled pages.

    So think of schema as removing friction rather than adding rocket fuel. It doesn’t force a ranking boost, but it clears the path for the clicks and citations that do.

    How Many Types of Schema Are There?

    Schema.org currently defines 797 types and 1,453 properties. That number is real, but it’s also misleading if you take it at face value, because most of those types exist for extremely narrow use cases you’ll never touch.

    In practice, a normal business website needs somewhere between 10 and 15 schema types, covering things like your organization, your pages, your content, and whatever you sell or offer. The rest of the catalog is there for edge cases: specific vehicle listings, music discographies, scientific datasets, and so on.

    The Main Types of Schema Markup

    Here’s every schema type that actually shows up on most websites, grouped by what they’re for.

    Business & Identity Schema

    Organization Schema:
    Establishes who’s behind the site: name, logo, official URL, and links to social profiles. This is the schema Google needs to build a Knowledge Panel for your brand. Build Organization Schema with the free Schema Markup Generator.

    LocalBusiness Schema:
    A more specific version of Organization for a physical location: address, hours, phone number, service area. LocalBusiness Schema is used by restaurants, clinics, stores, and any business people visit in person.

    Person Schema:
    Person Schema identifies an individual: name, job title, credentials, social links. Common on author bio pages and team pages, and useful for E-E-A-T since it gives search engines a verifiable identity behind the content.

    Content Schema

    Article Schema:
    Marks a page as a news piece, blog post, or editorial content, with headline, author, and publish date. Article Schema is what makes a post eligible for Google’s Top Stories and News carousels.

    Breadcrumb Schema:
    Breadcrumb Schema describes your site’s navigation path (Home > Category > Page), which shows up as a clean breadcrumb trail in search results instead of a raw URL.

    FAQ Schema:
    FAQ Schema marks up a question-and-answer format so it’s eligible to appear as an expandable dropdown directly in search results.

    HowTo Schema:
    Structures a step-by-step guide, including the tools, materials, and steps involved, so search results can show the process directly.

    Commerce Schema

    Product Schema:
    Covers price, availability, and product details on an ecommerce page. This Product schema type behind the price and stock-status text you see under shopping results.

    Review Schema:
    Attaches a rating and review content to another entity, like a Product or LocalBusiness. Review Schema is what generates the star ratings you see under some search results.

    Media Schema

    Video Schema:
    Describes an embedded video’s title, thumbnail, and upload date, making it eligible to show a video thumbnail directly in results.

    Recipe Schema:
    Covers ingredients, instructions, cook time, and nutrition info, and is what makes recipe cards with photos and ratings show up in search.

    Engagement Schema

    Event Schema:
    Marks up event details: name, date, location, and ticket information, so upcoming events can appear directly in search with dates and venue info.

    JobPosting Schema:
    Describes a job listing’s title, location, and hiring organization, which is required for a listing to appear in Google’s job search results.

    Course Schema:
    Covers a course’s name, provider, and description, useful for educational platforms and training providers.

    Navigation & App Schema

    Website Schema:
    Identifies your site as a whole and can enable a sitelinks search box directly in Google results.

    SoftwareApplication Schema:
    Describes an app or software product: operating system, category, and download link.

    ItemList Schema:
    Marks up an ordered list of items, useful for “best of” lists and ranked content.

    Speakable Schema:
    Flags specific sections of a page as suitable for text-to-speech, relevant for voice assistant results.

    SearchBulb’s free Schema Markup Generator covers all 18 of these types, with a form for each one so you never have to hand-write JSON-LD.

    How to Choose the Right Schema Type

    Verndale’s technical team frames this well as a short set of questions to ask for every page template, not just once for the whole site:

    1. What is this page mainly about?
      Pick the most specific type that matches, Article for a blog post, Product for a product page, not a generic catch-all.
    2. Who or what is responsible for it?
      Connect the page to the right Organization or Person entity.
    3. What can a user actually verify on the page?
      Only mark up information that’s visibly there. Don’t add a price, rating, or detail that isn’t shown to the visitor.
    4. Does it match the template?
      Implement schema dynamically through your CMS so it updates automatically when the page content changes, rather than hardcoding values that go stale.

    If a page genuinely covers more than one thing, like a blog post that includes a recipe, it’s fine to use more than one type together. Just make sure each one is accurate to what’s actually on the page.

    The Part Most Guides Skip: Building a Sitewide Schema Foundation

    Most schema tutorials treat each page as its own island: you add Product schema here, Article schema there, and call it done. That works, but it misses something more useful.

    A stronger setup connects your schema into one consistent structure. You define a single Organization entity with a stable ID, then every page’s WebPage schema references that same entity instead of repeating your business name, logo, and URL slightly differently each time. This avoids the common problem of search engines seeing several slightly different, conflicting versions of “your business” scattered across your own site.

    In practice, this means:

    • One Organization entity, defined once, in your global template
    • A WebPage entity generated per page, pulling from fields your CMS already has
    • Page-specific types (Article, Product, Event) layered on top of that foundation, not replacing it

    You don’t need to hand-build this graph structure from scratch. Getting the individual page-level types right with a free generator gets you most of the practical benefit without needing to engineer the full connected structure yourself.

    Common Schema Mistakes to Avoid

    • Using the wrong type for the page:
      Product schema on a category page, or Article schema on a static landing page, tells search engines something that isn’t true.
    • Marking up content that isn’t visible:
      If a rating, price, or detail only exists in your schema and not on the page itself, that’s a mismatch search engines can penalize.
    • Stacking unrelated types on one page:
      Just to try to win more rich result types. It reads as manipulative rather than descriptive.
    • Never testing it:
      Schema with a syntax error doesn’t throw a visible page error, it just silently fails to generate any rich result at all.

    How to Test Your Schema

    Google retired its old Structured Data Testing Tool, so the current standard is the Rich Results Test. Paste in a URL or your raw code, and it tells you whether the page is eligible for rich results and flags any errors.

    If you’re auditing schema across many pages at once rather than one at a time, that’s a bigger job than a single-URL tester is built for, but for validating a page before it goes live, the Rich Results Test is the standard.

    One thing worth checking alongside schema: if you’ve recently moved or renamed a page, confirm the redirect is set up correctly first. A broken or looping redirect can keep a page from being crawled at all, which means the schema on it never gets read no matter how correct the markup is. Our guide to redirect types covers exactly which redirect to use when, and you can verify any URL’s redirect chain with the free Redirect Checker.

    Build Your Schema Without Writing Code

    Reading about schema types is one thing. Actually generating valid, error-free JSON-LD for your specific page is the part that usually eats an afternoon.

    SearchBulb’s free Schema Markup Generator covers all 18 of the types in this guide. Fill in a plain-English form, and it builds clean, correctly formatted JSON-LD in real time, no account, no limits, and nothing to install.

  • Types of Redirects: Every Redirect Code Explained

    Types of Redirects: Every Redirect Code Explained

    If you’ve ever seen a “301 vs. 302” argument in an SEO Slack channel, you know redirects sound more complicated than they are. They’re not. There are really only a handful of redirect types you need to know, and most sites only ever use two of them.

    This guide is for anyone who manages a website, works in SEO, or just needs to fix a broken link without breaking their rankings in the process. By the end, you’ll know exactly which redirect to use, when, and why the wrong one can quietly cost you traffic.

    Quick summary — the redirect types that actually matter:

    • 301 (Moved Permanently) — the page moved for good; use this 90% of the time
    • 302 (Found) — the page moved temporarily; Google keeps the original indexed
    • 307 / 308 — stricter versions of 302 and 301 that preserve the request method
    • Meta refresh and JavaScript redirects — non-server alternatives, best avoided when you have a choice

    What Is a Redirect?

    A redirect is a way of automatically sending visitors, and search engines, from one URL to a different one. Instead of showing a “page not found” error, the browser quietly loads the new address.

    Technically, most redirects work through HTTP status codes, three-digit numbers a server sends to a browser. Any code starting with a 3 is a redirect. The server also sends a Location header telling the browser exactly where to go next.

    You’ll run into redirects constantly without noticing: typing example.com and landing on www.example.com, clicking an old blog link that lands on the updated post, or visiting a site that force-switches you from http:// to https://. All of those are redirects doing their job.

    Permanent vs. Temporary: The Split That Actually Matters

    Before you memorize individual codes, understand this one distinction. It decides everything else.

    Permanent redirects tell search engines the old URL is gone for good. Google drops the old URL from its index and transfers its ranking signals to the new one. Use these when a page has genuinely moved and isn’t coming back.

    Temporary redirects tell search engines the move is short-term. Google keeps the original URL indexed and doesn’t transfer ranking value to the new one. Use these for maintenance pages, limited-time promotions, or A/B tests.

    Mixing these up is the single most common redirect mistake. Use a temporary redirect for a permanent move, and your old page can keep hogging the index while your new page struggles to rank. Use a permanent one for something temporary, and you can lose your original page from search results entirely.

    The Main Types of Redirects (HTTP Status Codes)

    Here’s every redirect code you’re likely to encounter, and what each one is actually for.

    CodeNameTypeTypical use case
    301Moved PermanentlyPermanentPage moved for good; most common redirect on the web
    302FoundTemporaryShort-term move; original URL stays indexed
    303See OtherTemporaryRedirect after a form submission, so refreshing doesn’t resubmit it
    307Temporary RedirectTemporaryLike 302, but guarantees the request method doesn’t change
    308Permanent RedirectPermanentLike 301, but guarantees the request method doesn’t change
    300Multiple ChoicesSpecialRare — lets the browser show a list of options to pick from
    304Not ModifiedSpecialTells the browser to use its cached copy of the page

    301 Moved Permanently

    The default choice for almost every real redirect. If you’re merging pages, renaming a URL, fixing a broken link, or migrating to a new domain, this is what you use. It passes the bulk of the old page’s ranking authority to the new one.

    302 Found

    Use this when a page is unavailable right now but will come back. A flash sale page, a site under maintenance, or an A/B test are good examples. Google keeps showing the old URL in search results while the redirect is active. That’s exactly the point.

    303 See Other

    You’ll see this less often. It’s built for one specific job: redirecting a user after they submit a form or complete an action, so hitting the browser’s back button and refresh doesn’t accidentally resubmit the same data.

    307 Temporary Redirect

    Functionally almost identical to 302, with one difference: a 307 guarantees the browser won’t change the request method (say, from POST to GET) during the redirect. Most sites can use 302 without issue, but 307 is the technically stricter option when that distinction matters.

    308 Permanent Redirect

    It has the same relationship to 301 that 307 has to 302: a permanent redirect that preserves the original request method exactly. It was introduced specifically to remove ambiguity that 301 carried over from older, looser server behavior.

    300 Multiple Choices and 304 Not Modified

    These two are edge cases you’ll rarely configure yourself. A 300 lets a server offer several possible pages for one request, though you almost never see this in practice. A 304 isn’t really a redirect at all. It tells the browser “nothing’s changed, use what you already cached,” which speeds up load times rather than sending anyone anywhere.

    Other Ways to Redirect (Non-HTTP Methods)

    HTTP status codes aren’t the only way to redirect a page. Two other methods exist, and it’s worth knowing when to reach for them, and when not to.

    Meta refresh redirects live inside the page’s HTML, not the server response:

    html

    <meta http-equiv="refresh" content="0; url=https://example.com/new-page" />

    Google treats a meta refresh with 0 seconds as permanent, and anything above 0 seconds as temporary. These are slower than server-side redirects and are generally a fallback for when you don’t have access to your server configuration.

    JavaScript redirects work by changing the page location through code:

    javascript

    window.location = "https://example.com/new-page";

    These only work if the browser actually runs the script, which isn’t guaranteed for search engine crawlers. Google has said plainly that it only recommends JavaScript redirects when server-side and meta refresh redirects genuinely aren’t options, since rendering can fail and the redirect might go unseen entirely.

    One detail almost nobody mentions: if a page somehow has more than one of these three redirect methods set up at once, HTTP redirects always fire first, JavaScript redirects fire second, and meta refresh fires last, since it only triggers after the page has fully loaded. Knowing the order matters if you’re troubleshooting a redirect that doesn’t seem to be working the way you expect.

    Not All 3-Digit Codes Are Redirects — Clearing Up a Common Mix-Up

    You’ll find articles online that lump 4xx codes (like 404 Not Found) and 5xx codes (like 500 Internal Server Error) in with “redirect types.” That’s not accurate, and it’s worth being clear about why.

    A redirect sends a browser to a different, working URL. A 4xx code means the problem is with the request itself: the page truly doesn’t exist, or access is denied. A 5xx code means the server itself failed to process the request. Neither one redirects anybody anywhere. They just report an error and stop there.

    It’s a small distinction, but it matters if you’re diagnosing a broken page. A 404 needs a fix or a redirect to a working page — it isn’t a redirect on its own.

    How to Choose the Right Redirect Type

    A simple way to decide:

    1. Is the move permanent?
      Use a 301 (or 308 if you need the stricter method-preserving behavior).
    2. Is the move temporary?
      Use a 302 (or 307 for the stricter version).
    3. Are you redirecting after a form submission?
      Use a 303.
    4. Do you have server access?
      Always prefer a server-side HTTP redirect over meta refresh or JavaScript.
    5. Don’t have server access?
      A meta refresh set to 0 seconds is the next-best option.

    Redirect Best Practices

    Getting the code right is half the job. These habits prevent the other half of redirect problems:

    • Redirect to the closest matching page: Sending users to a page with completely different content is treated as a soft 404, so Google largely ignores the redirect and won’t pass along any ranking value.
    • Avoid redirect chains: If page A redirects to B, which redirects to C, fix it so A points straight to C. Google follows roughly 10 redirect hops before giving up, and every extra hop slows the page down and leaks a bit of ranking signal.
    • Avoid redirect loops: A redirects to B, and B redirects back to A. This breaks the page entirely, and browsers will show an error rather than load anything.
    • Update your internal links: If you redirect an old URL, go back and point your own internal links straight to the new one instead of routing them through the redirect.
    • Give redirects time: Google’s John Mueller has said search systems need to see a redirect consistently over time to fully register the change, and recommends keeping a redirect live for at least a year.

    If you’re planning a bigger site migration, it’s worth pulling every URL from your current sitemap first with a Sitemap URL Extractor so nothing gets missed in the move. It’s also worth double-checking your robots.txt isn’t accidentally blocking the new pages from being crawled.

    How to Check Which Redirects Your Site Is Using

    Reading about redirect codes is one thing. Seeing your actual redirect chain is another. If you’ve inherited a site, migrated a domain, or just want to confirm a fix actually worked, you need to see the real HTTP response, not guess from the browser.

    SearchBulb’s free Redirect Checker does exactly that. Paste in any URL, and it traces the full redirect path: every hop, every status code, and the final destination, so you can spot chains, loops, and wrong-code mistakes in seconds. No signup, no limits, and nothing gets stored on our end.

    The Bottom Line

    Most redirect confusion comes down to one choice: permanent or temporary. Get that right, pick 301 or 302 accordingly, and you’ll cover the vast majority of real-world situations. The other codes (303, 307, 308, 300, 304) exist for specific technical cases you’ll rarely need to think about day to day.

    If you’re not sure what’s actually happening on a URL right now, don’t guess. Run it through the free Redirect Checker and see the real answer.