In Short:
AI is now part of how architects and specifiers find products. If your product data isn’t set up right, it won’t show up in AI searches, no matter how good the product is. Your product data needs to be readable by machines, not just people. That means moving away from flat PDFs and toward web pages with clearly labeled details like product name, CSI division, and compliance codes written in formats AI can actually understand. Being listed in AIA MasterSpec (Specpoint) puts you in the room where specs are written. It’s one of the main places AI tools look when helping specifiers draft project specs. Consistently using the right CSI MasterFormat codes is how AI finds your product.
If your website, product listing, and submittal docs don’t all say the same division and section number, AI tools may skip your product entirely. PDFs alone won’t cut it anymore. AI can’t easily read PDFs the way it reads web pages, so a well-structured product page on your website should be your main source—with PDFs as a downloadable option.
An easy way to understand AI-assisted specification research is through an example. In this example, imagine you make and distribute vinyl windows.
Now, put yourself in the shoes of a project owner, developer or specifier putting this prompt into ChatGPT, Grok, or Google: “Most cost effective, weather-resistant vinyl windows for two 15-story mixed-use multi-family residential buildings.”
More Read
Several products come back in seconds, each with a citation showing how the windows meet the need, but yours isn’t on the list. Why did that happen? It’s not necessarily because your product underperforms, but that the AI couldn’t parse your data. This is the reality manufacturers and distributors are now facing.
While you’re working on making the best product available, let’s dive into the role AI now plays in getting those products visibility and how you can keep your goods discoverable. Why AI is Changing Where Specification Research Starts
The traditional path of product specification hasn’t disappeared. That’s when a manufacturer rep calls an architect and builds a relationship from there.
However, this is becoming more old school according to research from the American Institute of Architects (AIA), which says much early-stage specification research now begins with AI prompts. The AIA has documented howAI tools are reshaping the specification workflow, with design professionals increasingly using AI to not only find products, but to also cross-reference their code compliance, and even generate spec drafts.
More Read
Platforms like AIA MasterSpec®, powered by Specpoint, now embed AI assistance directly into the spec-writing environment. [3]
That all means the definition of “getting in front of specifiers” is now a bit different.
Instead of what reps can demonstrate in person or even on a video call, your product’s discoverability is also now tied to what AI can find and verify. How Do You Make Product Data Machine-Readable? Let’s first define what “machine-readable” product data is. Machine-readable product data refers to structured information presented in such a way that software can understand it without guessing. The most important word in that definition is “structured,” because AI research thrives on:
Having attributes labeled
Explicit values listed
Clearly defined relationships between values and attributes. For building products, that means moving beyond paper catalogs and flattened PDFs (ones where the text can only be read by human eyes) into web-native formats:
HTML product pages with clearly marked attributes, including product name, application, CSI division, compliance codes, and dimensions. Schema.org ProductSpec markup embedded in your site’s HTML.
This is the same markup that drives Google’s AI Overviews and other AI-powered search results. JSON-LD (JavaScript Object Notation for Linked Data) in the page header, which AI agents read without parsing visible content. Simply put, JSON is what websites have used to translate data to search engines for years. JSON-LD is just the next generation of that. Tagged technical data sheets that are HTML-native or properly tagged PDFs, not scanned images. Digital marketing agency Grupa Insight has published an article on its website that goes over applying these practices and has linked Schema.org markups to higher visibility in AI-generated searches.
More Read
Remember, for building product manufacturers, higher AI search visibility is your new direct line to getting specified. Audit Your Products for Machine-Readable Content
Before scrambling to make any changes to your website’s HTML, start with an audit of your highest-priority product pages.
Do they have labeled attributes in the page HTML, such as CSI division, applicable codes, and application type? If the answer to that question is either “no” or “it’s in a PDF,” that’s a problem.
The good news is that it’s a problem that can be solved with the steps below. What Documents Get Products Cited in AI Research? Keep in mind that not all documentation carries equal weight with AI. The format and location of your product content can determine whether it gets surfaced, cited, or skipped by AI. The documentation that tends to get building products cited:
AIA MasterSpec listings. With more than 50,000 products listed in Specpoint, MasterSpec is the product database specifiers and AI tools reference when writing specs. If your product isn’t listed or has outdated information, it will be skipped.
Structured web-based product pages. Pages with explicit attribute labeling will always beat PDFs because AI agents can easily extract and compare the data without interpretation. Code-compliance references in accessible format. IBC, ASTM, NFPA, and ICC references need to be embedded in product descriptions, and not just in a PDF appendix. Keeping evidence of compliance in an easily readable format helps AI verify that your product meets a specifier’s criteria.
Honestly, it also helps a person quickly find this information, as well. Guide specs written to your product. If a manufacturer guide spec exists and is publicly accessible, AI tools can cite it directly when generating draft sections. The AIA has noted that AI’s role in specifications includes “instant answers and insights through AIA MasterSpec and supporting documents.” [2] Without question, supporting documents must be 100% findable and readable to make that list. More manufacturer-focused resources on specification, and tips for how to improve specification positioning, can be found on ConstructConnect’s website. How Do Code-to-Spec Workflows Change Visibility?
Building product manufacturers should already know what MasterFormat division they belong to. But it’s likely many have not checked whether their product pages, listings, and submittal docs all say the same thing.
That brings us to another thing that AI requires: consistency. AI spec tools are looking through many sources and looking for those that are consistent with one another. Here’s an example: An AI tool drafting a Division 07 CSI code roofing spec won’t browse the open web to find just any roofing option. It will target sources already classified to Division 07. So, if your roofing product’s data isn’t associated with the right MasterFormat section in your product listings, on your web pages, and in your submittal documentation, no matter how quality or beloved your product is, it won’t show up in that spec. That risk can compound quickly.
Dan Cumberland, an AI consultant for construction and architecture firms, says, “CSI provides the common language across architects, engineers, contractors, and owners. In practice, every stakeholder downstream of the spec is supposed to inherit those codes.”
As Dan writes, that downstream process is where it can go downhill: “Construction CSI codes break down at handoffs. The code lives in the spec, but as work moves from estimator to PM to field to accounting, time pressure and tool fragmentation push entries into ‘misc’ — and once a cost lands there, it almost never moves back.”
Tying it back to AI, if the original classification is wrong or missing, every downstream workflow inherits that error … including AI-assisted specification. In practice, that means three things:
Verify your product pages reference the correct MasterFormat division and section number explicitly.
Ensure your MasterSpec listing is mapped to the right section. When writing guide specs or product descriptions, include the CSI section number. Never assume a specifier will take the time to look it up. Think of CSI classification as the raised flag that helps AI tools find your project, and not an administrative standard. Do Outdated PDFs Hurt Discovery? You can probably guess the answer by now, and it’s, “Yes, outdated PDFs hurt product discovery.” What’s more, the impact may be even more severe than you may think.
A company with product datasheets available only as PDFs has effectively blocked its product range from AI-assisted procurement research, regardless of that company’s popularity or product’s technical ability. When a buyer uses ChatGPT or Perplexity to compare specifications across competing products, PDF-walled information does not appear in that comparison. Why does that happen? There are two big reasons:
Unstructured content.
A PDF without proper tagging is essentially just an image to AI tools. The AI can’t easily extract attributes or compare values, and that will lead it to deduce the document can’t be cited with confidence.
Outdated content. PDFs can’t be updated like websites can.
A product datasheet still floating around the internet last updated in 2019, for a product that’s since been reformulated will lead to citation risks. AI tools may pull the wrong spec data or, much worse, flag the source as stale and deprioritize it moving forward. While it sounds like we’re bashing PDFs, we are not. We should be clear: The fix isn’t eliminating PDFs. Specifiers, engineers, and the public still use them.
The essential part is making sure your PDFs are matched with a structured and currently updated web-native record. A “web-native record” is as simple as a page on your website. Keep this rule in mind: Your datasheets are there to be downloaded by people. Your product webpages are what AI can actually cite. Consider Including an llms.txt File in Your Website
This is a rather new standard, but there has been a growing trend of adding an llms.txt file to websites.
The llms.txt is a publicly accessible, plain-text document that directs AI crawlers to your most authoritative product pages. BigCommerce, a retail solutions provider, has more on incorporating an llms.txt file into your website. What Spec-Positioning Data Tells You
Getting machine-readable is the first thing you need to do.
Knowing whether it’s working is the next question. Spec-positioning data answers that question. Spec-positioning data provides information on where and when your products are being written into specifications. It shows which markets, project types, and specifiers are selecting your products, and where competitors are winning spec mentions that should be yours. If your structured product pages are live, your MasterSpec listing is current, and you’ve addressed the PDF problem, but you’re still not showing up in specification research, spec-positioning data points to the gap. ConstructConnect’s 5 Tips for Increasing Your Specification Rate covers the tactical side of improving spec rate once the data foundation is in place.
Frequently Asked Questions (FAQs)
What format should my building product data be in for AI to read it? HTML with structured markup (Schema.org or JSON-LD) is the most reliable machine-readable format.
Product pages with labeled attributes (application, CSI division, compliance codes) can be parsed and cited by AI tools. PDFs can supplement but should not be your primary source. Does my product need to be on AIA MasterSpec to appear in AI specification research?
Not exclusively, but an AIA MasterSpec listing through Specpoint puts your product inside the platform specifiers use to write specs, including its AI-assisted features. It’s one of the most direct ways to enter the research environment where specification decisions are made. Why doesn’t my detailed PDF datasheet show up when specifiers use AI tools? PDFs without proper accessibility tagging are difficult for AI to read. The content may be there, but the structure isn’t extractable the way HTML content is. AI tools default to sources where the data is clean and explicitly structured, which is how an inferior product could be cited over a better one; the inferior product has all its info laid out in HTML, while the better product’s data is only in a flattened PDF.
How do CSI MasterFormat codes affect AI-assisted product research? AI specification tools use MasterFormat divisions and section numbers as their organizational framework.
Products explicitly associated with the correct division, such as in their listings, web content, and guide specs, are in the right location for those tools to find them. Products without clear CSI references can be missed even when the product is technically appropriate. What is spec-positioning data and how do manufacturers use it? Spec-positioning data tracks where your product is being specified: by whom, in which markets, on what project types, compared to competitor products.
Manufacturers use it to identify where they’re gaining traction, where competitors are winning specifications they should be winning, and where documentation improvements are most likely to move the needle.
