Bonsai Marketing / Foundation AssessmentKeep both. Split them by customer, not territory
Custom Pipe & Fabrication and ProFab Corporation both operate from Lubbock 79416, roughly three miles apart, serving an overlapping regional trade. Both keep their websites. The question this assessment answers is how to position them so they compound across the South Plains counties instead of cannibalising each other in the same local pack.
The answer is already encoded in their Google Business Profiles. Custom Pipe is categorised as a Manufacturer. ProFab is categorised as an Industrial equipment supplier. That is not an accident of setup — it is the real difference in what each sells, and it is the cleanest line to build the entire regional strategy along.
[ Data verified ] Google Business Profiles captured Aug 10 2026 — ProFab: Industrial equipment supplier, 5.0★ (3), 4002 N Frankford Ave, (806) 747-7272. Custom Pipe: Manufacturer, 4.0★ (10), 4717 US-84, (806) 767-0902. Regional keyword clusters pulled live Aug 10.
The core risk, stated plainly. Two businesses in the same zip code, in the same industry, chasing the same queries, will not both appear in a local pack. Google filters near-duplicate results. If both sites target "metal fabrication Lubbock," the most likely outcome is that one gets filtered and the other ranks weakly — worse for the group than either would do alone. Differentiation is not a nice-to-have here. It is the thing that decides whether two entities is an advantage or a self-inflicted wound.
Not sister companies — a parent and a subsidiary
This review was requested as a comparison of two sister companies under a common parent. The public record shows a different structure: Custom Pipe & Fabrication, Inc. acquired ProFab Corporation in March 2026. Custom Pipe is the parent. ProFab is the subsidiary.
[ Data verified ] Acquisition announcement at custompipe.com/custom-pipe-acquires-profab/; Water Well Journal; ABNewswire release, March 4 2026.
That distinction changes the analysis in three ways. These are not two brands to be balanced — one is an acquirer with scale and authority, the other an acquired asset with neither. The strategic question is not which is performing better, but what ProFab should become and what Custom Pipe does with it. And the single most valuable move available to ProFab is not an SEO tactic at all: it is being formally attached to its parent in a way machines can read.
The comparison that follows is framed as an integration analysis rather than a scorecard contest. Where the two businesses are assessed independently, the full detail lives in the companion reports: Custom Pipe & Fabrication and ProFab Corporation.
The numbers, without commentary
| Dimension | Custom Pipe | ProFab | Gap |
|---|---|---|---|
| Overall Foundation Score | 34 / 100 | 26 / 100 | CP +8 |
| Monthly organic traffic | 1,229 | 14 | CP 88× |
| Ranking keywords | 552 | 132 | CP 4.2× |
| Branded traffic | 1,022 (83%) | 0 (0%) | opposite failures |
| Non-branded traffic | 207 | 14 | CP 15× |
| Referring domains | 251 | 124 | CP 2× |
| — of which genuine | ~40 | ~4 | CP 10× |
| Indexed pages | 314 | 40 | CP 7.9× |
| Sitemap URLs | 145 | 7 | CP 21× |
| Blog posts | 32 | 1 — hello-world | — |
| Technical resources | 35 | 1 | CP 35× |
| Physical locations | 13 (9 states) | 1 (Lubbock) | — |
| AI Overview coverage | 5.1% | 0% | both critical |
| Local pack coverage | 4.3% | 0% | both weak |
| Keywords in top 10 | 69 (12.9%) | 6 (4.4%) | CP 11.5× |
| Usable meta descriptions | 0 of 14 sampled | 6 of 6 | ProFab ahead |
| Keyword-led titles | none | all | ProFab ahead |
| Structured data | none | Yoast defaults only | both inadequate |
| Approved fixes not being served | 473 (pixel off, frozen) | n/a | cheapest fix available |
| Search Console connected | No | n/a | blind to manual actions |
| Crawl coverage | 14 of 145 pages | 7 of 7 | CP under 10% |
| Hosting | WP Engine + Cloudflare | bare Apache, HTTP/1.1 | CP ahead |
Scale without hygiene, hygiene without scale
This is the most useful finding in the review, and it is the reason a coordinated program beats two independent ones.
Custom Pipe — scale without hygiene
145 URLs, 13 plants, 32 articles, 35 technical resources, NSF certification, AWWA presence, 50 years of history — and not one meta description, not one line of structured data, a homepage titled "Custom Pipe," and a sitemap declaration that returns 404.
It has built a large house and never wired it.
ProFab — hygiene without scale
Six pages, every one carrying a keyword-led geo-targeted title and a real meta description. Correct canonicals, clean sitemap, legacy URLs properly retired. Someone did the on-page work competently.
There is simply almost nothing to apply it to — and the name on the door is shared with thirty other companies.
Neither company's weakness is the other's weakness. That is unusual, and it is the strategic opening: the fixes are complementary rather than duplicative. ProFab's on-page discipline is a working template for what Custom Pipe needs across 145 URLs. Custom Pipe's authority and content library is exactly what ProFab has none of.
What they do share
- Neither has meaningful structured data. Custom Pipe has none at all; ProFab has Yoast's defaults and no Organization, LocalBusiness, Product or Service schema. Between them: fourteen physical plants, zero machine-readable location data.
- Neither is present in AI search. 5.1% and 0% AI Overview coverage. In a category where buyers increasingly ask an AI system "who fabricates X," both companies are absent from the answer.
Each holds what the other is missing
Custom Pipe leads on
- Authority — 251 referring domains including nsf.org (DA 49), AWWA, trade press
- Scale — 21× the indexed surface, 13 locations, national footprint
- Content — 67 real assets versus effectively zero
- Brand equity — #1 for every branded variant
- Infrastructure — managed hosting behind a CDN
ProFab leads on
- On-page discipline — 6/6 pages optimized versus 0/145
- Technical hygiene — correct canonicals, working sitemap, legacy URLs retired
- Geographic clarity — every title names Lubbock; Custom Pipe's name nothing
- A clean homepage — never carried injected third-party content
That last point is not incidental. Custom Pipe's homepage carried hidden Greek-language casino copy with a live outbound affiliate link — found during this assessment on Aug 5, removed by their developer, and independently verified clean on Aug 7. ProFab's never did. A page nobody was monitoring carried unauthorized content for an unknown period, and nothing in the stack flagged it.
Where the failure modes rhyme
| Risk | Custom Pipe | ProFab | Severity |
|---|---|---|---|
| Spam injection / policy exposure | resolved Aug 7 access path unknown | none | Watch |
| Toxic backlink cluster | present — prlog.ru + ~20 farms | ~97% of profile | High |
| No structured data | total absence | defaults only | High |
| AI search absence | 5.1% | 0% | High |
| Local pack underperformance | 4.3% across 13 plants | 0% | High |
| Single-page traffic dependency | homepage = 379 of 552 kw | homepage = 102 of 132 kw | Med-High |
| Product pages at zero traffic | both hubs at 0 | 17 kw, 0 traffic | Medium |
| Entity name inconsistency | 3 names in market | 30+ same-named firms | High |
Both concentrate essentially all organic visibility on a single page. Both have product pages that rank for nothing. Both carry link profiles that need cleanup. The causes differ; the exposure is the same.
Product or project — the line that separates them
The GBP categories already draw the line. The job is to make the websites, the service pages and the county pages say the same thing consistently enough that Google treats them as two different businesses rather than two listings for one.
| Custom Pipe & Fabrication | ProFab Corporation | |
|---|---|---|
| GBP category | Manufacturer | Industrial equipment supplier |
| What it sells | Engineered product to spec — column pipe, spools, fittings, discharge heads, waterworks | Fabrication capability — build-to-print, custom stainless & carbon steel, machining |
| The buyer | Water-well drillers, pump distributors, municipalities, irrigation contractors | Plant maintenance, ag operations, industrial contractors, one-off custom work |
| How they buy | Catalogue + spec sheet + lead time | Drawing + quote + turnaround |
| Search language | column pipe, ductile fittings, waterworks supply, pipe fabrication | machine shop, welding, metal fabrication, steel fabricators |
| Trade hours | Opens 7 AM | Opens 8 AM |
| Review base | 4.0★ (10) | 5.0★ (3) |
Read the search language row again — it is the whole strategy. Nobody searching "machine shop Levelland" wants a column-pipe catalogue, and nobody searching "ductile iron fittings" wants a job shop. These are genuinely different buyers using genuinely different words. The two entities are not competing for one customer; they are two front doors for two customers who happen to live in the same counties.
Three ways to run this, and what each costs
All three keep both entities and both websites. They differ in what separates them.
Option 1 — Split by customer type recommended
Custom Pipe owns product language. ProFab owns capability language. Each builds its own county pages, in its own vocabulary, for its own buyer. GBP categories stay as they are and the sites are rewritten to match them.
Why it works: it is the only split Google can actually perceive. Different categories, different service pages, different query language means two distinct entities rather than two competing listings. It also matches how the businesses genuinely differ.
Cost: both sites need real service-page builds. ProFab's six pages must become a capability structure; Custom Pipe's two product hubs must become a product catalogue.
Risk: discipline. The moment ProFab writes a "pipe fabrication" page or Custom Pipe writes a "machine shop" page, the split collapses.
Option 2 — Split by territory
Both do similar work; carve the counties. Custom Pipe takes the north and east (Hale, Floyd, Crosby, Lamb), ProFab takes the south and west (Terry, Gaines, Yoakum, Dawson).
Why it is weaker: Google does not honour negotiated territory. Both plants sit in the same Lubbock zip, so both are equally proximate to every query in the region — a searcher in Brownfield gets whichever listing Google prefers, not the one you assigned. Territory splits work for field-service businesses with dispersed locations, not two shops three miles apart.
Where it does help: as a content layer applied on top of Option 1 — each entity writes county pages for its own category. That is additive, not an alternative.
Option 3 — Tiered front door
ProFab becomes the regional walk-in and small-job entry point — fast turnaround, local trade, smaller tickets. Custom Pipe handles engineered, spec-driven and municipal work. ProFab passes anything large or spec-heavy upstream.
For: mirrors how many acquired shops actually operate; gives ProFab a clear, defensible role; makes the referral path explicit rather than accidental. Reinforces Option 1 rather than replacing it.
Against: it depends on an operational reality we cannot verify from outside — whether ProFab is genuinely set up to take small local jobs, or is a production facility feeding Custom Pipe contracts. If it is the latter, ProFab has no local customer to market to and Option 1 alone is the answer.
Recommendation: Option 1, with Option 2 applied as a content layer and Option 3 adopted only if operations support it.
Split by customer type, because it is the only difference Google can see and the only one that reflects the businesses honestly. Then let each entity build county pages across the South Plains in its own vocabulary — Custom Pipe writing product and water-systems language for Hale, Floyd, Crosby and Lamb; ProFab writing fabrication and machining language for Terry, Gaines, Yoakum and Dawson — so the geographic layer multiplies the category split rather than substituting for it.
The one rule that makes it work: a query belongs to exactly one entity. Write it down, and enforce it in every page title, H1 and GBP service list. Every time both sites chase the same phrase, the group loses a local pack it could have won.
Assets that should flow between the properties
Regardless of which option is chosen, five moves transfer value the group already owns:
- Reciprocal linking. profab.net already links to custompipe.com 21 times. The relationship is entirely one-directional. Custom Pipe should link back contextually — passing authority from the property that has it to the property that does not.
- Shared credentials. NSF/ANSI 61 certification, AWWA participation and fifty years of history are group assets. ProFab's pages display no certifications at all.
- Content transfer. Custom Pipe's 67 assets cover subject matter directly relevant to ProFab's capabilities — HSLA steel, ductile iron fabrication, stainless spools, Protecto 401. Coordinated cross-publishing with correct canonicals closes a multi-year gap without commissioning multi-year content.
- Infrastructure consolidation. Move profab.net onto WP Engine behind Cloudflare. One-time migration, permanent security and performance benefit.
- A single entity graph. Organization on Custom Pipe with ProFab as
subOrganization; Organization on ProFab with Custom Pipe asparentOrganization; LocalBusiness on all fourteen plants. This is the move that makes the group legible to AI systems as one coherent manufacturer with fourteen facilities, rather than two unrelated small sites.
The group's honest balance sheet
Strengths
- 50 years (Custom Pipe) and 40 years (ProFab) of operating history
- 14 plants across 9 states after the acquisition
- NSF/ANSI 61 certification — verifiable, hard to replicate, category-critical
- AWWA participation and trade-press coverage
- 67 existing content assets in the group
- Complementary capabilities: national systems + regional precision fabrication
- Custom Pipe's branded search position is unassailable
- ProFab's on-page discipline is a working template for fixing the parent
Weaknesses
- Unauthorized cloaked content live on the parent's homepage
- No meaningful structured data anywhere — 14 plants, zero machine-readable locations
- 83% branded dependency and 0% branded presence — opposite failures, both bad
- Both link profiles carry substantial spam
- Product pages across both properties generate no traffic
- 26 half-complete branch pages instead of 13 strong ones
- ProFab's name is shared with 30+ competitors
- Two hosting stacks, two content programs, no shared entity graph
Opportunities
- 18,520/mo traffic potential on a difficulty-7 flagship cluster
- 87 page-two keywords movable with on-page work alone
- 14 local markets with near-zero current local pack presence
- AI search: competitors are equally absent — the category is genuinely unclaimed
- Content transfer from parent to subsidiary closes years of gap at low cost
- The acquisition itself is a PR and authority asset
- Case studies and project galleries — zero across both, highest-persuasion asset class
Threats
- Google spam action against custompipe.com — domain-level, and the access path is still open
- US Pipe at 21,993 monthly visits — 17.9× the parent, compounding
- AI answer engines resolving category questions without either company present
- Post-acquisition drift — the acquired brand starving while attention goes to integration
- Both link profiles accumulating spam passively
- Zero non-branded insulation if a competitor targets the category seriously
One program across both properties
Contain, decide, lay foundation
- Critical Reinstall the delivery pixel + unfreeze the project — ships 473 approved fixes — Custom Pipe
- Critical Read the homepage revision history to identify the injection's access path — Custom Pipe
- The ProFab decision — who owns Lubbock (see §08) — both
- Fix the 404ing sitemap declaration — Custom Pipe
- Deploy the shared entity graph — Organization, parent/subOrganization, LocalBusiness ×14 — both
- Titles + meta descriptions across all 145 URLs — Custom Pipe
- Add the missing homepage H1; delete
hello-world; clean archives — ProFab - Claim and optimize all Google Business Profiles — both
- Begin disavow review on both link profiles — both
Local and commercial foundation
- Consolidate duplicate branch URLs into 13 complete local pages — Custom Pipe
- NAP and entity-name standardization across all directories — both
- Rebuild the two product hubs as genuine commercial pages — Custom Pipe
- Build capability pages — stainless, carbon steel, machining, pump components — ProFab
- Attack the 87 page-two keywords with on-page work — Custom Pipe
- Establish reciprocal contextual linking — both
Content authority and proof
- "Pipe Fabrication" capability hub targeting the 1,655/mo flagship — Custom Pipe
- Topical clustering of the existing 67 assets into hub-and-spoke structure — Custom Pipe
- Industry pages — municipal water, agricultural irrigation, industrial process — ProFab
- Case studies and project galleries — currently zero across both — both
- Technical resource libraries with gated high-value downloads — both
- Lubbock ownership review — is the local cluster moving? — both
AI visibility and compounding
- FAQ and Service schema across all commercial pages — both
- Entity authority program — Wikidata, industry directories, trade citations — both
- AI-retrieval content: technical Q&A structured for citation by answer engines — both
- Local content programs for the 13 branch markets — Custom Pipe
- Digital PR targeting AWWA, NGWA and trade publications — both
- Measurement review — AI Overview coverage, non-branded traffic, local pack — both
A note on projections. This assessment deliberately does not publish a traffic or revenue forecast. Doing so credibly requires inputs only leadership holds — average order value, close rate on inbound enquiries, sales-cycle length, and capacity per plant. What is verifiable: the flagship cluster carries 18,520 monthly traffic potential at difficulty 7, and Custom Pipe currently captures 207 non-branded visits per month against it. The gap is the opportunity. Sizing it in dollars is a conversation, not an estimate.
If nothing else happens this quarter
- Write down which entity owns which query. One list, enforced in every title, H1 and GBP service entry. Custom Pipe takes product language; ProFab takes capability language. This single document prevents the two sites from filtering each other out of the local pack.
- Fix Custom Pipe's Lubbock branch page. It publishes (806) 787-8886 plus two (714) Anaheim numbers. The Google Business Profile says (806) 767-0902. Three numbers, one of them from the wrong state, none matching the profile — on the page meant to establish a Texas location.
- Switch Custom Pipe's delivery back on. 473 approved optimizations — titles, meta descriptions, schema, alt text — are written, approved and reaching nobody. A configuration change, not a project.
- Ship LocalBusiness schema on both, with the county service areas named. Neither entity has any today. This is what turns two claimed profiles into two machine-readable regional businesses.
- Build county pages in each entity's own vocabulary. Levelland, Plainview, Brownfield, Littlefield, Slaton, Post, Seminole, Lamesa. Difficulty across the regional cluster runs 8–16 and neither entity holds any of it.
Bottom line for leadership. Two entities in one region is an advantage or a liability depending entirely on whether they are distinguishable. Right now they are three miles apart, in the same zip, with overlapping trade and no differentiation on either website — which is the liability configuration.
The fix does not require choosing between them or merging them. It requires deciding, once and in writing, which customer each one is for — and then saying that consistently across two sites, two profiles and every county page you build. The Google categories already say it. The websites do not say it yet.
Neither entity currently appears in a single local pack. That is the whole opportunity: the regional market is not lost, it is unclaimed.
Let's map the query split.
Thirty minutes to divide the regional vocabulary between the two entities and sequence the county build.
Book a Call with Bonsai Marketingfikeshway@bonsaimarketingcompany.com · (707) 593-7539