# Great Lakes Dredge and Dock Company > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-11-06. - **Brand record:** https://optimly.ai/brand/great-lakes-dredge-and-dock-company - **Dataset:** https://optimly.ai/brand/great-lakes-dredge-and-dock-company.json - **Markdown:** https://optimly.ai/brand/great-lakes-dredge-and-dock-company/llms.txt - **Official website:** https://gldd.com - **Slug:** great-lakes-dredge-and-dock-company - **Categories:** construction-engineering ## Overview - **Tagline:** Great Lakes Dredge & Dock Corporation (GLDD) is a leading U.S. dredging contractor providing dredging, coastal protection, land reclamation, and offshore energy services. Source: Brand's website (https://gldd.com) · 2026-11-06 - **Description:** Headquartered in Houston, Texas, Great Lakes Dredge & Dock Company is the largest provider of dredging services in the United States and performs significant international projects. GLDD operates approximately 200 specialized vessels and serves domestic coastlines, inland waterways, and selected international markets. Source: Brand's website (https://gldd.com) · 2026-11-06 ## Identity - **Mission:** To improve and protect infrastructure and coastlines through innovative, high-quality dredging and marine construction work, with a focus on safety, environmental protection, and enhancement. Source: Brand's website (https://gldd.com) · 2026-11-06 - **Founders & leadership:** Lasse Petterson is identified on the website as President and CEO of Great Lakes Dredge & Dock Corporation. Source: Brand's website (https://gldd.com) · 2026-11-06 - **Website:** https://gldd.com Source: Brand's website (https://gldd.com) · 2026-11-06 - **Voice & tone:** Corporate, technical, safety-focused, environmentally responsible, and service-oriented. Source: Brand's website (https://gldd.com) · 2026-11-06 - **Founded:** 1890 Source: Brand's website (https://gldd.com) · 2026-11-06 - **Headquarters:** Houston, Texas, United States Source: Brand's website (https://gldd.com) · 2026-11-06 - **Parent ownership:** Part of the Saltchuk family of companies. Source: Brand's website (https://gldd.com) · 2026-11-06 ## Offerings - **Problem solved:** GLDD helps maintain and deepen navigation channels and ports, protect and restore coastlines, reclaim land, restore rivers, lakes, and reservoirs, and stabilize subsea infrastructure for offshore energy projects. Source: Brand's website (https://gldd.com) · 2026-11-06 - **Core capabilities:** - Channel and port maintenance - Channel deepening and port expansion - Coastal protection and restoration - Land reclamation - River, lake, and reservoir dredging - Offshore energy subsea rock installation - Environmental and habitat restoration - Marine engineering, project management, and production planning Source: Brand's website (https://gldd.com) · 2026-11-06 - **Products / SKUs:** - Dredging services - Coastal protection and restoration services - Land reclamation services - Rivers, lakes, and reservoir dredging services - Offshore energy subsea rock installation Source: Brand's website (https://gldd.com) · 2026-11-06 ## Audience - **Target industry:** Dredging, marine infrastructure, coastal protection, port and navigation infrastructure, environmental restoration, and offshore energy. Source: Brand's website (https://gldd.com) · 2026-11-06 - **Customer base:** Clients requiring dredging, marine infrastructure, coastal protection, environmental restoration, and offshore energy services, including port, navigation, shoreline, and offshore energy projects. Source: Brand's website (https://gldd.com) · 2026-11-06 - **Use cases:** - Maintaining channels and ports - Deepening navigation channels and expanding ports - Protecting and restoring shorelines, beaches, barrier islands, and coastal marshes - Reclaiming land and developing aquatic infrastructure - Restoring capacity in rivers, lakes, and reservoirs - Installing subsea rock to protect offshore wind infrastructure and export cables - Restoring marine and coastal habitats Source: Brand's website (https://gldd.com) · 2026-11-06 - **Customer outcomes:** - Improved and protected navigation infrastructure and coastlines - Enhanced coastal resilience and mitigation of storm and sea-change risks - Expanded or maintained port and channel capacity - Restored land, waterways, reservoirs, and sensitive habitats - Protected subsea offshore energy infrastructure - Project execution with an emphasis on safety and environmental protection Source: Brand's website (https://gldd.com) · 2026-11-06 Page last updated 2026-11-06. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.