Plain-language guide
Eight hundred to fifteen hundred words on one question, with headings, a short process list and an invitation to visit. Best for search and for managers who forward links.
RankGuarantee™ SEO
Local landing pages built in volume, for every city you serve.
Rank on page 1 for 100+ local keywordsRank for 100+ local keywordsRank for 100+ Local Keywords
Included in all Organic Growth plansFree in every Organic Growth plan $1,495/moOrganic Growth
SEO, Google Maps, and AI search (GEO) working as one plan.
SEO, Google Maps & AI search in one planSEO, Maps & AI in one planSEO, Google Maps & AI Optimization
Includes RankGuarantee™ + a custom websiteRankGuarantee™ + website included $895/moPaid Ads
Google, Bing & Meta campaigns managed end-to-end for fast leads.
Google, Bing & Meta Ads for fast leadsGoogle, Bing & Meta AdsGoogle, Bing & Meta Ads Management
Get results in days, not monthsResults in days, not monthsFew people read about sediment removal for pleasure. They read about it the week a pond stops draining, a board asks for options or a boat cannot reach its slip. Content marketing for a dredging contractor means being the clearest explanation they find that week. A good guide answers the question, builds trust and leads naturally to a site visit request. This page covers which topics fit the trade, who should write them, how technical claims are checked and how the guides support SEO. GetPhound is an online marketing company, and content is part of our search plans.
Why guides work here
A manager comparing three proposals for pond dredging often cannot tell why they differ. One includes dewatering and hauling, another assumes the owner handles the material, a third excludes restoration of the banks. Without context, the cheapest looks best and the most thorough looks expensive. A contractor who publishes a plain explanation of what belongs in a proposal helps the buyer compare fairly, and may be remembered as the company that explained things.
The same applies to board members who know nothing about the work. They are asked to approve money for something they cannot picture. A well-written page, with photographs and a simple sequence of steps, gives a manager something to share with the board. That sharing is a kind of referral, and it happens quietly.
Guides also serve search. People type questions, and pages that answer them may appear in results and in AI answers. A site with a dozen honest, specific guides has a better chance of being found than one with a services page and a contact form.
Topic map
| Topic | Buyer stage | Who it helps | Link toward |
|---|---|---|---|
| Signs a pond needs sediment removed | Early | Owners noticing shallow water or smell | Pond page |
| What drives the cost of pond dredging | Budgeting | Managers and boards | Site visit request |
| Hydraulic or mechanical removal: how to choose | Comparing | Engineers and informed owners | Methods page |
| What a bathymetric survey is | Early to mid | Everyone who must define the scope | Process page |
| What happens to the removed material | Mid | Managers worried about trucks and odor | Process page |
| Permits and agencies: who to ask | Mid | Owners starting a project | A general note that rules vary |
| How long a project takes and what changes it | Mid | Boards planning around seasons | Process page |
| Working around golf play or boating season | Mid | Clubs and marinas | Matching service page |
| Stormwater pond care and when removal is needed | Early to mid | Property managers | Pond page |
| How to compare dredging proposals | Comparing | Anyone collecting bids | Contact page |
| Before and after: a lake project explained | Late | Boards wanting reassurance | Gallery |
| A seasonal planning checklist for associations | Planning | Associations setting budgets | Guide download |
Formats
Long-form page
Eight hundred to fifteen hundred words on one question, with headings, a short process list and an invitation to visit. Best for search and for managers who forward links.
Visual page
A sequence from survey to cleanup with a picture at each step. Good for boards and residents.
Short page
A few paragraphs about one finished project, with permission and honest detail. Builds proof.
Table-driven
Hydraulic and mechanical removal side by side, with where each fits. Good for engineers.
Embedded clip
A one-minute walk through a finished pond or a drone flyover. Useful on project pages and in Meta Ads.
Lead magnet
A planning checklist or questions to ask contractors, offered in return for an email address with consent.
Who writes what
The best dredging content starts with your experience. An estimator who has walked many ponds can tell us the things owners say, the surprises on site and the questions that come up on the third visit. We interview, draft and edit, then ask a named person at your company to review every technical statement before publication. That person approves facts about methods, equipment categories and handling. We handle structure, headings, search phrasing, internal links and publishing.
Nothing technical goes live without approval. Statements about permits are written generally and checked against the idea that rules differ, not against a specific rule. Statements about environmental outcomes, engineering results or costs are kept out unless you can document them. This is slower than copying generic text, and it protects you.
Calendar
Publish the cost drivers page and the process explainer. Fix thin service pages.
Hydraulic or mechanical removal, and what a survey is. Add photographs.
How to compare proposals and the agencies owners should check, written generally.
Two finished projects described honestly, with permission.
A planning checklist for associations, ahead of budget season.
Check which pages bring calls, update the weak ones and plan the next six months.
Keeping it safe
Some content ideas are risky. Avoid statements about environmental benefits that you cannot support, such as claims about improved water quality or wildlife. Avoid engineering claims about capacity, flood protection or structural performance. Avoid specific permit rules from one place that readers in another might rely on. Avoid promised timelines and prices. Avoid naming customers without permission, and avoid photographs that show private details.
Replace risky statements with honest framing. Instead of saying a project improved water quality, describe what you did and what the owner reported, in their words and with their permission. Instead of quoting a rule, say that agencies differ and owners should check with the relevant federal, state and local offices. This is both safer and more credible.
Draft to published
| Step | Who does it | What happens |
|---|---|---|
| Pick the question | Estimator and us together | A real question a manager or owner asked, in their words |
| Interview | Estimator | A short conversation about how it works in practice |
| Draft | GetPhound | Structure, headings, plain language and internal links |
| Technical review | A named person at your company | Facts about methods, equipment categories and handling checked |
| Photographs | You | Real images with owner permission, described accurately |
| Publish and link | GetPhound | Page goes live, linked from related service pages |
| Review later | Both | After a few months, check visits and calls and refresh if needed |
Examples
The most requested page is also the hardest to write honestly. A strong cost drivers page opens by saying that no two projects cost the same, and then explains why. It describes how the volume of sediment shapes the work, how access and staging space affect the method, how the material is dewatered and moved, how disposal or reuse is arranged and how restoration of banks or access roads is handled. It mentions that survey work and permits are part of the picture and that approvals vary by location.
It then tells the reader what to prepare for a site visit: the location, a rough description of the water, any past surveys and the purpose of the work. It invites them to request a visit and explains what happens next. It does not print a per-unit price or a range, since either could be quoted back to you out of context. Buyers who read a page like this arrive as better-informed callers, and the quote conversation starts from understanding.
Pitfalls
Wrong audience
Jargon about cutter heads and discharge lines may impress peers but confuses a manager. Explain terms in plain words.
Wrong rules
Permit and handling rules differ by place. Write generally and tell readers to check local agencies.
Stale pages
A guide with old details loses trust. Review twice a year.
Weak proof
Dredging is visual. Even a few images lift a page.
Lost inquiries
Every guide should end with a clear way to request a site visit.
SEO links
Every guide should link to a page that can act on what it taught. A cost guide leads to the site visit form, a method guide to the methods page and a process explainer to the pond or lake page. In return, the service pages link to the guides so a visitor who needs more detail can find it. This internal linking is a major part of how search engine optimization for dredging companies works, and it also helps the people who read the site. The link building page explains how guides attract mentions from associations and engineers.
Pricing
Content answers
Content is included in Organic Growth plans: Silver at $1,495 a month with four assets, Gold at $2,495 with eight assets and a managed website and Platinum at $3,495 with twelve. There is no setup fee or contract.
A named person at your company reviews every technical claim before publication. We do not publish anything you have not approved.
Long enough to answer the question. Many useful guides run between eight hundred and fifteen hundred words, with headings and a short process list.
Yes, with the owner's permission and without private identifying details.
They give buyers and search tools something clear to read. Results vary, and we do not promise rankings. We track visits, calls and forms.
Only in general terms. Say that rules differ and owners should check with agencies.
Yes. A method comparison page in plain technical language serves them and informed owners.
Explore more
Get in Touch
Tell us the questions owners and managers ask you most, the projects you are proudest of and who in your company can review technical statements. We will suggest a first set of guides. Call 610-825-4363 or email hello@getphound.com and our CEO will answer your questions.
