Google Posts for fishing guides
Builds guide sites for a livingPublished July 22, 2026Last updated July 26, 202612 min read
- Post content may not include a phone number; attach a call button drawn from the verified profile instead.
- The posts policy incorporates the Maps content rules, which name repetitive content and personal information as violations.
- Omitting information that could unduly affect a booking decision falls under misrepresentation, so date your posts and photographs.
- A client's face is personal information and needs consent; your own name and face as a public-facing operator do not.
- Regulatory actions are published months before they take effect, which turns posting from invention into scheduling.
Google will not let you put a phone number in a post. Not as a courtesy, not as a style preference: the policy names the behaviour, calls it phone stuffing, and says the content is not allowed to contain one.
That single rule tells you what the field is for. A post is not a small advertisement, and the platform has already decided that the number belongs on a button drawn from your verified profile rather than in the text. What the field is actually for is stated in the same document: communicating relevant and timely information to customers. For a guiding operation that phrase has an unusually literal answer, because the timely information in this trade is published in advance by the federal government. Related pieces sit together on the getting-booked hub.
| Item | Position |
|---|---|
| A phone number in the post text | Not allowed |
| A call button drawn from the verified profile | Allowed instead |
| Business contact details generally | Merchants may post their own |
| The same post repeated | Treated as repetitive content |
| A named client's face without consent | Personal information |
What is a post for, in Google's own words?
Relevant and timely information, which is narrower than it sounds.
The policy opens by saying you can use your Business Profile to communicate relevant and timely information directly to your customers.
Both adjectives are load-bearing. Relevant excludes the generic, and timely excludes the evergreen.
It also states you are responsible for making sure posted content complies with all applicable laws and regulations, which is a heavier sentence than most people read it as.
And it notes that the policies are occasionally modified, that you should check back for updates, and that notice of changes will be given where the law requires it.
So the field is a bulletin board with legal exposure attached, rather than a feed.
Treating it as a feed is why most guide profiles have three posts from two seasons ago.
Google publishes this in its photos, videos and posts content policy.
Why can a post not carry a phone number?
Because the policy names the abuse and closes the route.
The policy says that to avoid the risk of abuse, post content is not allowed to include a phone number.
Instead you can attach a call button to the post, which uses the number already verified on your profile.
That is a better outcome than the workaround it replaces, because the button is tied to a verified number and cannot drift out of date the way pasted text does.
The same document shows how vertical-specific these rules get: hotels are barred from creating offer posts, or any post mentioning or linking to deals, promotions, special offers or discounts, so that customers are not confused about where to find organic and advertised prices.
Guiding operations are not hotels and that restriction is not aimed at you, but it demonstrates that post types are gated by trade rather than uniformly available.
Which is worth remembering before anybody sells you a posting strategy built on a feature your profile may not have.
Which fields a number genuinely belongs in is settled by the profile setup piece.
What else does the posts policy pull in?
The prohibited and restricted content rules, in full.
The posts policy is short because it incorporates the Maps user generated content policy by reference, and that document is where the substance lives.
It covers impersonation, misinformation, misrepresentation, harassment, hate speech, offensive content, personal information, unclear content, repetitive content and defacement.
Most of those will never trouble somebody posting a tide report, and two of them are worth a guide's attention because they are easy to trip accidentally.
The document also states the consequences plainly, saying actions may range from suspending account privileges to account termination, and that it considers content, account information, user actions and whether a pattern of harmful behaviour exists.
Reading it once takes about ten minutes and removes the guesswork permanently.
The two provisions that catch guides are the subject of the next two sections.
The separate rules governing what you attach to a post are handled by the profile photos piece.
What counts as misrepresentation in a post?
Less than you would think, and omission counts.
The policy prohibits misleading or deceiving others, and lists false or misleading accounts of the description or quality of a good or service.
It also lists distorting or omitting facts to scam other users, and, more broadly, distorting or omitting information that could have an undue impact on user decision making.
That last clause is the one worth sitting with, because omission is a form most people do not consider a claim at all.
A post showing a stringer of fish from a species whose season closed last month, with no date on it, is omitting information that bears directly on somebody's decision to book.
A post promising a species you can no longer legally target is a false account of the service.
Neither requires bad intent, and neither is fixed by a disclaimer nobody reads.
The fix is small: date the post, state what the trip actually targets now, and let last year's photograph be visibly last year's.
Whose face is allowed to appear?
Yours, freely. Anybody else's, with consent.
The policy says not to distribute or post personal information without consent, and defines personal information as information applying to a living identifiable person where disclosure could risk harm if compromised or misused.
Its enumerated examples include a person's full name or last name, and their face in a photograph or a video.
A client's face in a post is therefore squarely inside the definition, which is a stricter reading than most operators apply to a grip and grin.
The policy is equally explicit about what merchants may do: it allows merchants to post contact information related to their business, including a phone, email or social media handle.
It also allows an individual's name where it is part of the commonly known or advertised business entity, or where the person is a public-facing professional conducting business under their own name.
A captain trading under their own name is squarely in that second allowance, so your name and face are fine and your client's are a question you have to have asked.
How to ask, and when, is set out in the photo permission piece.
Does repetition matter?
Yes, and it is named as its own violation.
The policy prohibits repetitive content, defined as posting the same content multiple times from the same account or from multiple accounts, on the stated ground that it dilutes the useful information Maps provides.
It separately prohibits unclear content, giving as its example content that lacks meaning across languages, such as a random group of characters.
The practical consequence for a guide is that a weekly post reading "great day on the water, DM to book" is not a strategy. It is the same post fourteen times.
The policy also rules out off-topic content, saying only to post content based on experience at a specific location and disallowing general, political or social commentary or personal rants.
Read together, those three push in the same direction, which is that a post must carry information that did not exist last week.
Which brings the question round to what, in this trade, actually changes week to week.
The general version of that question is worked through in the content calendar piece.
What is genuinely timely for a guide?
Regulatory change, and it is published months ahead.
On 17 June 2026 NOAA Fisheries published a final rule at 91 FR 36545 implementing measures under the reef fish management plan for the Gulf.
Its own abstract states that the rule modifies the Gulf Other Shallow-Water Grouper complex catch limits and sets a recreational fixed closed season for that complex.
The stated purpose is to reduce harvest of Gulf scamp and yellowmouth grouper while the council develops a further amendment considering additional measures.
The rule is effective on 1 January 2027, which means it was published six and a half months before it changed anything.
That gap is the whole opportunity. A guide who reads it in June can post about it in June, again in November, and again the week it lands.
Three posts, each carrying information the reader could not have known, each unambiguously relevant and timely, all from a document that costs nothing to read.
The rule is published by the Federal Register, and the section it amends sits on eCFR. Confirm the current text before you post about a date, since rules of this kind are amended and superseded.
How many post-worthy events a season actually holds. Count what genuinely changes in a year for one operation: two or three regulatory actions affecting species it targets, a handful of season openings and closings, a few tide series worth naming, one or two changes to the operation itself such as a new boat or a new trip type, and the shift into and out of the off-season. That is somewhere around twelve to twenty events, which at one post each is a post every two to four weeks. Set against the alternative, which is a weekly post that repeats itself and falls under the repetitive content prohibition, fewer and better is both the compliant answer and the practical one. The twelve to twenty is reasoning from the shape of a season, not a measurement, and no posting frequency, view count or engagement figure is asserted here for any profile.
Why does the lead time change the job?
Because it turns posting from reaction into scheduling.
Most posting advice assumes the material arrives when it arrives, so the operator has to be present and creative on demand.
Regulatory material behaves in the opposite way. It is published, dated, and effective later, which means the post can be written the day you read it and held.
A rule published in June and effective in January gives you a window most trades would envy, and the work is reading rather than inventing.
It also produces posts nobody else in your market is making, since almost no operation reads the rules that govern it until the week they bite.
The reader gets something genuinely useful, which is the stated purpose of the field, and you get to write it in a month when you are not on the water at five.
None of that requires a subscription, a tool or a writer.
The same discipline applied to your own site pages is described in the water and city pages piece.
What does a usable post look like?
One change, one date, one consequence, no number.
Name the thing that changed, in the words a client would use rather than the words the rule uses.
Give the date it takes effect, because a date is what makes a post timely rather than merely relevant.
State the consequence for somebody booking a trip, which is the only part most readers actually need.
Attach a photograph that is genuinely from the water and the season being discussed, not the best frame you own from four years ago.
Use the call button rather than typing a number, since the policy does not allow the number in the text.
Keep it to a few sentences, because a post carrying one fact clearly beats a post carrying five vaguely.
Then stop, and do not post again until something else has changed.
The surrounding search work these posts feed into belongs to the local search piece.
Where do guides go wrong here?
Seven ways, and two of them are named violations.
Typing a phone number into the post, which the policy prohibits outright as phone stuffing.
Posting the same message every week, which falls under the repetitive content prohibition.
Posting a client's face without having asked, which the personal information rules treat as a disclosure.
Reusing an old photograph of a species that is now closed, undated, which is omitting information bearing on a booking decision.
Posting general commentary rather than something tied to a specific place and experience, which the off-topic rule addresses directly.
Abandoning the field for two seasons and then wondering why the profile looks derelict.
And treating the post as an advertisement when the policy describes it as information, which is the mistake underneath the other six.
The field for answering questions before they arrive is treated in the profile questions piece.
What tends to surprise people?
That the restrictions are published and specific.
Most operators assume the posts field is unpoliced, and it inherits a policy document listing named violations with named consequences.
The second surprise is the phone number rule, because it is counterintuitive until the call button is explained, and then it is obviously better.
The third is that omission is treated as a form of misrepresentation, which is a stricter standard than most marketing operates under.
The fourth is that the genuinely timely material for this trade is free, published, dated in advance and read by almost nobody.
The fifth is how few posts a year that implies, which is a relief rather than a limitation.
Taken together the field rewards an operator who reads, which is not how most people imagine local search working.
The reviews side of the same profile runs on a different part of the same policy, covered in the reviews strategy piece.
What does not belong in a post?
Five things, and the first is now settled.
A phone number, in the text, under any formatting.
A named client, or a recognisable client's face, without their consent.
An undated photograph doing work that implies it is current.
A claim about what a trip will produce, since the description and quality of a service is exactly what the misrepresentation rule covers.
And anything you have already posted, which the repetitive content rule addresses by name.
What is left after those five is a short, dated, factual note about something that changed, which is what the field was built for.
The services list that sits beneath those posts is described in the services piece.
Is the field worth the time at all?
On this reading of it, yes, and cheaply.
No published figure exists for what posts do to a profile's visibility, and none is asserted anywhere on this page.
What can be said is structural. The field is free, it accepts information your competitors are not reading, and its main cost is the reading rather than the writing.
Twelve to twenty short posts a year, each carrying one dated fact, is a few hours of work spread across a calendar.
Whether that produces bookings is answerable only in your own market, by asking clients where they saw you, over a full season.
Anybody quoting you a percentage lift from posting is quoting something they cannot source, and it is fair to ask them where it came from.
The honest position is that the field is cheap, compliant to use well, and unmeasured.
How the surrounding ranking mechanics actually work is examined in the map pack piece.
How would you audit what is up now?
Four checks, about twenty minutes.
Open every live post and note its date, because anything older than the current season is answering a question nobody is asking.
Check each for a phone number in the text, and remove it in favour of the call button.
Check each photograph for a client's face, and for whether you actually asked.
Check whether any two posts say substantially the same thing, and delete the later one.
Then read one regulatory action affecting a species you target, and write the post it produces before you close the tab.
That last step is the only one that adds anything, and it is the one people skip.
The category that decides which searches see any of it is chosen in the categories piece.
The posting habit, in order
Read the rules, write the post, hold it, publish on the date.
Subscribe to or check the federal publications covering the fisheries you work, which is a bookmark rather than a subscription.
When an action lands, write the post the same day, in client language, with the effective date in it.
Hold it, and publish once when you read it and once as the date approaches, without repeating the wording.
Never put a number in the text. Attach the call button instead.
Use a photograph from the water and the season you are describing, with nobody in it whose permission you have not got.
Say what changed and what it means for a booking, then stop.
Aim for something like a post a fortnight across a year, and let a quiet month be quiet.
And ask every booking client where they saw you, because that log is the only measurement available.
No posting frequency or performance figure appears here. There is no view count, engagement rate, visibility lift or ranking effect stated here for Business Profile posts, whether for guiding operations or anybody else, and no market is excepted. Reading behind this page turned up nothing published of that kind, and no estimate was written to occupy the space. The platform policies were read on 26 July 2026 and Google states it modifies them occasionally; the fisheries rule quoted is a federal action that may be amended or superseded, so confirm the current position before posting about a date. Nothing here is legal advice.
How this was checked. The posts rules are quoted from Google Business Profile Help, Business Profile photos and videos policy and posts content policy, at support.google.com/business/answer/7213077, read in full on 26 July 2026. Quoted from it: that you can use your Business Profile to directly communicate relevant and timely information to your customers; that the prohibited and restricted content policies apply to submitted or published content including text, photos and videos; that you are responsible for making sure posted content complies with all applicable laws and regulations; that the policies are occasionally modified, that readers should check back for updates, and that notice will be provided where required by applicable law; that under the heading of avoiding phone stuffing, and to avoid the risk of abuse, post content is not allowed to include a phone number, with a call now button using the verified Business Profile phone number offered instead; and that hotel businesses cannot create offer posts or any post mentioning or linking to deals, promotions, special offers or discounts, so customers are not confused about where to find organic and ad prices. The incorporated content rules are quoted from the Maps user generated content policy, prohibited and restricted content, at support.google.com/contributionpolicy/answer/7400114, read the same day: the misrepresentation provisions covering false or misleading accounts of the description or quality of a good or service, distorting or omitting facts to scam other users, and distorting or omitting information that could have an undue impact on user decision making; the personal information provisions defining personal information as information applying to a living identifiable person where disclosure could result in risk of harm if compromised or misused, enumerating a full name or last name and a face in a photograph or video, while allowing merchants to post contact information related to their business including phone, email or social media handles, and allowing an individual's name where it is part of the commonly known or advertised business entity or where they are a public-facing professional conducting business under their name; the repetitive content provision covering the same content posted multiple times from one or several accounts; the unclear content provision; the off-topic provision requiring content based on experience at a specific location and disallowing general, political or social commentary or personal rants; and the enforcement statement that actions may range from suspending account privileges to account termination, taking into account content, account information, user actions and whether a pattern of harmful behaviour exists. The fake engagement, rating manipulation, review solicitation, harassment, hate speech, obscenity and terrorism provisions of that document were read but are deliberately not relied on here. The regulatory example is quoted from the NOAA Fisheries final rule at 91 FR 36545, Reef Fish Fishery of the Gulf of America; Shallow-Water Grouper Management Measures, document 2026-12175, published 17 June 2026 and effective 1 January 2027, retrieved from the Federal Register API on 26 July 2026: its abstract stating that the rule implements measures described in a framework action under the reef fish fishery management plan as prepared by the Gulf Council, modifies the Gulf Other Shallow-Water Grouper complex catch limits, sets a recreational fixed closed season for that complex, and is intended to reduce harvest of Gulf scamp and yellowmouth grouper while the council develops a further amendment. The body of that rule beyond its abstract, action and dates fields was not retrieved, and the codified section it amends is cited but not quoted. The arithmetic panel reasons from the shape of a season and contains no measurement. Nothing here is legal advice.
If your booking calendar has more open weeks than you’d like, I’ll build you a free preview of your booking site before you pay a cent.
Get a free website previewPosts, the policy behind them and what to put in one
Can I put my phone number in a Google post?
No. Under a heading about avoiding phone stuffing, the policy states that to avoid the risk of abuse it does not allow post content to include a phone number. Instead you can attach a call button to the post, which uses the number already verified on your Business Profile. That is a better arrangement than the workaround it replaces, because a button tied to a verified number cannot drift out of date the way pasted text does. The same document shows how specific these rules get by trade: hotels are barred from creating offer posts, or any post mentioning or linking to deals, promotions, special offers or discounts.
What is the posts field actually for?
The policy says you can use your Business Profile to directly communicate relevant and timely information to your customers. Both adjectives do work: relevant excludes the generic, timely excludes the evergreen. It also states that you are responsible for making sure posted content complies with all applicable laws and regulations, and that the policies are occasionally modified, so you should check back for updates, with notice given where the law requires it. So it is closer to a bulletin board with legal exposure attached than to a social feed, and treating it as a feed is why so many guide profiles carry three posts from two seasons ago.
Which other rules apply to posts?
The posts policy is short because it incorporates the Maps user generated content policy, and that is where the substance lives. It covers impersonation, misinformation, misrepresentation, harassment, hate speech, offensive content, personal information, unclear content, repetitive content and defacement. It also states the consequences plainly, saying actions may range from suspending account privileges to account termination, and that it weighs the content itself, account information, user actions and whether a pattern of harmful behaviour exists. Most of it will never trouble somebody posting a tide report, but two provisions are easy to trip by accident: personal information and repetitive content.
Can I post a photo of a client?
Only with their consent. The policy says not to distribute or post personal information without consent, and defines personal information as information applying to a living identifiable person where disclosure could result in risk of harm if compromised or misused. Its enumerated examples include a person's full name or last name and their face in a photograph or video, which puts a client's face squarely inside the definition. The same policy allows merchants to post contact information related to their own business, including phone, email or social media handles, and allows an individual's name where it is part of the commonly known or advertised business entity, or where they are a public-facing professional conducting business under their own name.
Is posting the same thing weekly a problem?
Yes, and it is a named violation. The policy prohibits repetitive content, defined as posting the same content multiple times from the same account or from multiple accounts, on the stated ground that it dilutes the useful information Maps provides. It separately prohibits unclear content, and rules out off-topic content by requiring posts to be based on experience at a specific location while disallowing general, political or social commentary and personal rants. Read together those push the same way: a post has to carry information that did not exist last week. A weekly note reading 'great day on the water' is not a strategy, it is the same post fourteen times.
What counts as timely information for a fishing guide?
Regulatory change, and it arrives with months of notice. On 17 June 2026 NOAA Fisheries published a final rule at 91 FR 36545 implementing measures under the reef fish management plan for the Gulf. Its abstract states the rule modifies the Gulf Other Shallow-Water Grouper complex catch limits and sets a recreational fixed closed season for that complex, to reduce harvest of Gulf scamp and yellowmouth grouper while the council develops a further amendment. It is effective 1 January 2027, six and a half months after publication. A guide who reads it in June can post about it in June and again as the date approaches, each time carrying something the reader could not have known.
How many posts a year does that work out to?
Fewer than most advice suggests, and that is the compliant answer as well as the practical one. Count what genuinely changes in a year for one operation: two or three regulatory actions affecting species you target, a handful of season openings and closings, a few tide series worth naming, one or two changes to the operation itself, and the shift into and out of the off-season. That is roughly twelve to twenty events, or a post every two to four weeks. The alternative, a weekly post that repeats itself, falls under the repetitive content prohibition. No published figure exists for what posts do to visibility, and none is asserted here.
Sources & methods
- Business Profile photos & videos policy and posts content policy, Google Business Profile Help
- Reef Fish Fishery of the Gulf of America; Shallow-Water Grouper Management Measures, 91 FR 36545
- 50 CFR 622.34, the codified section the rule amends (eCFR)
Every figure here is traced to a named public source and checked against it. Licensing, tax, and fee rules change. Verify your state’s current rules with the agency directly before you count on any number here.
Evan Knox
I build booking websites and run the ads and search for owner-run fishing guides, one operation per stretch of water. My first guide client, Bowman Fly Fishing, grew its revenue 4x in a year from that work. Field Notes is where I put the straight numbers on the business of guiding.
More field notes
Posts keep you fresh. A booking site turns interest into trips.
I'm Evan, and the guide whose Google profile stays active and leads somewhere anglers can book is the one who fills a calendar. I build booking sites and run the search and local SEO for owner-run guide operations, one operation per stretch of water, so a fresh, findable profile turns into trips. Text me at (470) 777-9686 and I'll build you a free preview of your site before you pay a thing.