What an assistant can and cannot fetch
An assistant that searches the web fetches pages the way a crawler does. It works best on a normal web page with text on it, at a stable address, that anybody can open without signing in.
- A login wall stops it. Much of a social platform sits behind one, and what a signed out visitor sees is often a fraction of the post.
- Images do not carry their words. Your price list posted as a graphic is invisible as text, no matter how clear it looks to a person.
- Video carries even less. A great explanation in a reel is, to a crawler, a file.
- Posts scroll away. A page has one address that stays put. A post is a moment in a feed.
- Captions are written for the feed, not for a question. They rarely state your city, your hours or your prices plainly, because your followers already know.
None of that is a criticism of Instagram. It is a description of a different job.
What your Instagram is actually good for
- Proof. Somebody who heard your name checks your grid before they call, and the work has to look like the work.
- Recency. An account posting this week says the business is alive, which is a real question in people's minds.
- Personality and staff, which no structured data field can carry.
- A place your existing customers already are, for asks like reviews and rebooking.
So keep posting. Just stop expecting it to do a job it is not built for. In our checks, when an AI answer names local businesses, the pages it cites are websites, directories and review sites far more often than social profiles.
The transfer: turn your best posts into pages
You have already written the content. It is sitting in your captions. The work is moving it somewhere readable.
- Open your last few months of posts and find the ones that answered a question. What does it cost, does it hurt, how long does it last, what should I do first.
- Give each of those questions its own page, titled the way somebody would ask it.
- Write the answer in the first paragraph, in the same plain voice you used in the caption.
- Put the photo on the page as well, with the explanation as real text beside it rather than inside it.
- Add your city, your hours and your contact details as text on the page.
- Add FAQPage structured data for the questions. See LocalBusiness schema for small businesses.
One good page per real question beats thirty posts, for this purpose. And the page keeps working next year, which the post does not.
The link in bio problem
Many local businesses point their bio at a link hub page instead of their own website. For a person that is a small convenience. For a machine it is a page of links with no facts on it, at a domain that is not yours, standing between the profile and everything you actually want read.
Point the bio at your own site. If you need several destinations, build that page on your own domain, and put your name, city, services and phone number on it as text. Then add your social profile addresses to the sameAs field in your structured data, so the profiles and the site are tied together as one business rather than several.
What to keep doing, and what to skip
- Keep posting the work, keep replying to messages, keep using it as proof.
- Keep your profile name, city and contact details identical to your listings.
- Skip paying for followers or engagement. It does nothing here and it is obvious.
- Skip putting your prices only in a graphic. Put them on a page as text as well.
- Skip treating a follower count as visibility. Being followed is not the same as being found.
- Skip the assumption that resharing a page link to your story counts as publishing it. Publish the page.
Method. Anything written here as in our checks is our own observation from running the same buyer questions in ChatGPT, Perplexity and Google AI Mode in a fresh logged-out session, month after month, most recently in September 2026. Third-party figures are linked in the sources beside this guide. Where a tool's behaviour is documented by the vendor, we describe the documentation rather than our guess at it.