← Back to blog

FAQ Schema for Self-Storage Sites: What Still Works in 2026

November 10, 2026
FAQ Schema for Self-Storage Sites: What Still Works in 2026

FAQ schema is structured data that labels the questions and answers on a page so machines can read them cleanly. Since May 2026, it no longer earns expandable FAQ answers in Google results. It is still valid markup, and for a storage facility it works best as one part of a bigger set: FAQPage on your real FAQ content, SelfStorage or LocalBusiness markup on every location page, and review markup only where Google's rules allow it.

This guide covers what changed, what to mark up on a storage site, the JSON-LD to use, and the mistakes that cause trouble.

Corvanesystems
corvanesystems.com
Make Your Facility Easier to Find
Corvane Systems combines technical SEO, local search positioning, and AI visibility work for self-storage operators.
Explore search visibility services

TL;DR

  • Google stopped showing FAQ rich results on May 7, 2026, so FAQ schema will not give you extra space on the results page.
  • FAQPage is still a valid Schema.org type. Keeping it does no harm, and you do not need to rip it out.
  • Your highest-value markup is LocalBusiness (or its SelfStorage subtype) with accurate address, hours, phone and price range.
  • Reviews you collect about your own facility are not eligible for star snippets, so never mark up ratings that are not visible on the page.
  • Use FAQPage when your team writes the answer. Use QAPage only when visitors can submit competing answers.

Table of Contents

What FAQ schema is, in plain terms

FAQ schema is a block of code, usually JSON-LD, that tells a search engine "this page contains these questions, and these are the answers." It uses the FAQPage type from Schema.org, which describes a page presenting a set of frequently asked questions. Each question is marked as a Question, and each one carries an acceptedAnswer with the answer text.

The code does not change what visitors see. It sits in the page source and mirrors the visible Q&A on the page. On a storage site, that means your "What size unit do I need?" and "Do you offer climate control?" answers, written once for people and labeled once for machines.

Is FAQ schema still relevant?

Yes, with a smaller job than it had before. Google dropped FAQ rich results from Search in May 2026, after having already limited them to well-known government and health sites in August 2023. Google also said it would retire the FAQ search appearance, the rich result report and Rich Results Test support for FAQ in June 2026, with Search Console API support ending in August 2026.

What that means for you:

  • No more expandable answers under your listing. If a plugin or agency promised them, that promise is out of date.
  • No need to delete working markup. Google's own 2023 guidance said site owners could drop FAQ structured data but did not have to remove it, because unused structured data causes no problems in Search. It just has no visible effect there.
  • The type remains valid. Schema.org still defines FAQPage, so the markup remains a clean, standard way to describe question-and-answer content.

The practical shift is in how you judge the work. Stop asking "will this get me a rich result?" Ask "does this page state clear, accurate answers that a person, a search engine or an AI assistant can lift without guessing?" Structured data is one input to that. The visible writing is the bigger one. Our guide to rewriting storage FAQ answers so AI tools can cite them covers the writing side.

Where FAQ markup still makes sense on a storage site

Mark up FAQ content when it is real, visible and written by you. Good places:

  • A main FAQ page covering unit sizes, access hours, insurance, payment, move-in steps and gate access.
  • Location pages, with questions specific to that facility: climate-controlled availability, vehicle parking, the office's hours, nearby landmarks.
  • Unit-type pages, such as a 10x10 page that answers "What fits in a 10x10?"

Skip it where the page has no visible Q&A. Marking up questions that readers cannot see on the page breaks the basic rule that markup must match page content.

If you are deciding what to publish in the first place, see what FAQ content a self-storage site should include.

FAQPage or QAPage: which one fits

The choice comes down to who writes the answers.

SituationType to use
Your team writes one definitive answer per questionFAQPage
Visitors can post their own answers to a question, forum styleQAPage
A page with a single question and several user repliesQAPage

A storage operator's FAQ page is almost always FAQPage. Google documents QAPage separately for pages in question-and-answer format, and it is built for community content. Using QAPage on content you wrote yourself is a mismatch. Using FAQPage on a page where visitors submit answers is the same mismatch in reverse.

In FAQPage, use acceptedAnswer for your official answer. suggestedAnswer belongs to the user-answer model.

FAQ schema code you can adapt

Here is a starting point in JSON-LD for a storage FAQ page. Place it in the page's HTML, in the head or body, and replace the text with your own answers. The text in the code must match the answers visitors can read on the page.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What size storage unit do I need for a two-bedroom apartment?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most two-bedroom apartments fit in a 10x15 unit. Call our office or visit and we will help you confirm the size."
      }
    },
    {
      "@type": "Question",
      "name": "Do you offer climate-controlled units?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Climate-controlled units are available at this location in several sizes. Check the unit page for current availability."
      }
    }
  ]
}

The sample answers are placeholders. Only publish statements that are true for your facility. If you do not have climate control, do not write that you do.

How to add and check it

  1. Write the visible Q&A on the page first, with each answer short and complete.
  2. Paste the JSON-LD into the page. Most content management systems and website builders allow a custom code block per page.
  3. Make sure the question and answer text match what is on screen.
  4. Validate the syntax with the Schema Markup Validator, which checks Schema.org markup in general. Google's Rich Results Test is dropping FAQ support, so do not rely on it for this type.
  5. Watch Search Console for general structured data errors on the page after it is crawled.

Our 11-step schema markup rollout for storage gives copy-paste templates for the full set of pages.

LocalBusiness schema: the markup that matters most

For a storage operator, the markup with the most direct local value describes the facility itself. Google's local business structured data documentation lists name and address (as a PostalAddress) as required. It recommends geo coordinates with at least five decimal places, openingHoursSpecification, telephone, url and priceRange.

Schema.org has a SelfStorage subtype, so you can state exactly what you are rather than a generic business. A published SelfStorage JSON-LD example shows a typical shape: name, a full postal address, telephone, hours, price range, URL and amenityFeature entries for things like climate control, 24/7 access and vehicle storage. The same example notes that SelfStorage does not produce a rich result on its own, and that it works as the backbone alongside other markup.

Self-storage facility with vehicle storage area

A trimmed version for one location:

{
  "@context": "https://schema.org",
  "@type": "SelfStorage",
  "name": "Your Facility Name",
  "url": "https://www.example.com/locations/your-city",
  "telephone": "+1-555-555-0100",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main Street",
    "addressLocality": "Your City",
    "addressRegion": "ST",
    "postalCode": "00000",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 00.00000,
    "longitude": -00.00000
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
      "opens": "09:30",
      "closes": "18:00"
    }
  ]
}

Three habits keep this markup useful:

  • Match your Google Business Profile exactly. Name, address, phone and hours should agree across the website, the profile and the markup. Differences make your data harder to trust.
  • One location, one page, one block. Each facility's page carries its own markup with its own address. Do not paste the same block across every location. Our location page playbook shows how to structure those pages.
  • Keep it current. When hours change for a holiday or a season, update the page and the markup together.

Review and AggregateRating schema: know the rule before you mark up stars

Many operators want star ratings beside their listing, and review markup is where well-meaning sites get into trouble. Google's review snippet guidelines say that when the business being reviewed controls the reviews about itself, pages using LocalBusiness or other Organization markup are ineligible for the star review feature. That includes reviews placed directly in the markup and reviews shown through an embedded third-party widget, such as Google Business or Facebook reviews.

For a storage facility, that has clear consequences:

  • Reviews of your own facility, collected on your own site, will not earn stars in results.
  • Do not add aggregateRating to your SelfStorage markup to try to get them. Google recommends aggregate ratings for sites that collect reviews about other local businesses, not for a business rating itself.
  • Never mark up a rating or review count that visitors cannot see on the page. Google's structured data guidelines require markup to represent the page's content truthfully, and ratings that are invented or not shown can lead to a manual action.

Your reviews still do real work. They shape your Google Business Profile, they persuade the person reading your page, and you can show them as visible testimonials. They just should not be dressed up as star-rating markup on your own pages.

Schema for AI search: what to expect and what to avoid

Searchers now get answers from tools like ChatGPT, Claude, Perplexity and Google's AI Overviews. It is natural to ask whether schema helps there. The honest answer is that structured data gives machines a clear, consistent description of your facility, and clarity is the goal. No markup guarantees a citation, and nobody outside these platforms can promise how any of them weigh it.

What you can control:

  • Facts stated plainly in visible text. Unit sizes, features, access hours, address and phone should appear in the HTML of the page, not only in images or scripts. Our piece on server-rendered facts for AI recommendations goes into this.
  • Markup that agrees with the page. JSON-LD that contradicts the visible text creates confusion rather than clarity.
  • Consistent facts across the web. Your website, Business Profile and directory listings should tell the same story.
  • Topical depth. Covering a subject thoroughly, as in our semantic SEO guide for storage, gives both search engines and AI tools more to work with.

If you want a baseline of where you stand, a visibility audit checklist walks through how a facility shows up across search and AI tools.

A sensible markup plan for a storage operator

In order of priority:

  1. SelfStorage or LocalBusiness on every location page, with complete address, phone, hours, geo and price range.
  2. FAQPage on pages with real visible Q&A, written by your team.
  3. Organization markup on the home page with your logo and official profiles.
  4. Breadcrumb markup where your site uses breadcrumb navigation.
  5. No self-serving review markup. Show reviews as visible content instead.

Then check the basics: pages get indexed, markup has no errors, and details match your profile. Our walkthrough of Search Console for storage operators shows how to monitor that without drowning in data.

Common mistakes to avoid

  • Marking up hidden content. If visitors cannot read the answer on the page, it does not belong in the markup.
  • Stuffing promotional copy into answers. Answer the question first. A sales pitch in every answer reads badly and gives machines nothing clean to extract.
  • Using the wrong type. FAQPage for your authored answers, QAPage only for user-submitted ones.
  • Copying one block everywhere. Each page's markup must describe that page.
  • Letting data go stale. Old hours or a retired phone number in code is worse than no code.

Our view: schema is plumbing, not strategy

We work only with self-storage operators, and the pattern is consistent. Facilities that treat schema as a trick are always chasing the last change. The ones that treat it as plumbing, the accurate, boring description of the facility, are never caught off guard when a rich result disappears.

The FAQ rich result going away is a good example. The operators who wrote useful, specific answers still have those answers working for them, in the page, in search and in AI tools. The ones who only added code to get a visual perk lost the perk.

That is why our system pairs technical and on-page SEO with local search work and AI-focused content. The markup, the Google Business Profile, the location pages and the articles all need to say the same true thing about your facility, in a form both search engines and AI systems can read. We built it for storage alone, so the templates, the questions and the priorities fit how renters actually search for units.

If you do one thing this month, make your location pages complete and consistent. Everything else builds on that.

Mike

Get the markup and the content handled together

Writing JSON-LD for one page is easy. Keeping it accurate across locations, alongside fresh content, a healthy Business Profile and monthly reporting is the real workload. Corvane Systems covers that for self-storage operators: technical and on-page SEO, local search, 30 AI-optimized articles a month, AI visibility audits and performance tracking.

Corvanesystems

The full Corvane system is $299 per month with a one-time $50 onboarding fee, no contracts and no minimums. You can also request a free AI visibility audit to see how your facility appears today, or ask about custom websites built for storage operators.

FAQ

Does FAQ schema still help SEO?

Not through rich results, which Google stopped showing on May 7, 2026. The markup is still valid and harmless, and the visible FAQ content it describes can still earn traffic and answer renters' questions. Treat the schema as a tidy label for good content, not a ranking lever.

Should I remove FAQ schema from my storage website?

You do not have to. Google has said unused structured data does not cause problems in Search, though it has no visible effect there. Remove it only if it no longer matches the visible page content, since mismatched markup is the real risk.

Can I add review stars with LocalBusiness schema on my own site?

Google's guidelines make pages ineligible for star snippets when the business controls reviews about itself, including through embedded widgets. Show your reviews as visible testimonials, and never add ratings to markup that are not visible on the page.

What is the difference between FAQPage and QAPage?

FAQPage is for pages where your team writes one answer per question. QAPage is for pages where visitors can submit their own answers, like a forum. A storage FAQ page you write yourself should use FAQPage.

Sources