Ledger

How to control goldenrod in a prairie

Written by Mark Vande Haar | Sep 9, 2026, 2:47:53 AM

Using a Late Season Spring Burn to Knock Back Canadian Goldenrod (Watch Video Here)

Standing at the edge of this unit, the line is about as clear as it gets. On one side, a late season burn. On the other, no burn. Same ground, same seed bank, same goldenrod pressure — and a pretty dramatic difference in what's standing there now.

Before anything else: this was a test

Two acres. Hillside. Burned June 5th.

The site is a smooth brome pasture — not CRP ground, not a remnant, not anything I'd have been sick about losing. Brome sod with goldenrod moving in from the timber edge. That's the whole reason it was a candidate.

I want that stated plainly up front, because the difference is dramatic enough that somebody's going to read this and go torch forty acres in June. Do this as a small, controlled test, on smooth brome or on an extreme problem area — and nowhere else until you've watched your own ground respond to it. Two acres is enough to learn something and small enough that being wrong is cheap.

If you're on CRP, stop and read your contract before you go any further. Burn timing is spelled out in your conservation plan, mid-contract management has approved windows, and growing season burning during primary nesting season is not something to improvise your way into. Talk to your county office first.

What "late season" means here

When I say late season burn, I'm talking about a late season spring burn — anytime after the warm season grasses start to show. In the Midwest that's typically May and June.

That's a different animal from the dormant-season burns most people are used to. A March or early April burn happens before much of anything is awake. It clears thatch and cycles nutrients, and the perennials come back swinging. Waiting until the warm season grasses break puts fire on the landscape at a moment when different plants are in very different places in their yearly cycle — and that's the whole lever.

The problem: goldenrod taking over

Goldenrod had gotten established on the far side of the treeline and worked its way into this area. That's how it usually goes. It doesn't arrive all at once; it creeps in from an adjacent patch, and once it gets a foothold it spreads by rhizome as much as by seed. Give it a few seasons of no disturbance and it goes from "one of the forbs out there" to "the forb out there."

That's the point where a lot of people start looking for options. A dense goldenrod stand crowds out the diversity you were managing for in the first place, and it's stubborn enough that mowing alone tends to just buy you a season.

On this particular hillside you're really dealing with two problems stacked on each other: brome sod underneath, goldenrod taking over on top. Neither one is what you want, and there's nothing under them worth protecting. That combination is what made a June burn worth testing here instead of somewhere I'd actually have something to lose.

What the late burn did

The goldenrod did not like that fire.

In the burned area you can still find goldenrod — it's not eradicated, and there are a couple of small patches inside the unit that didn't carry fire and came through more or less untouched. But compared to the unburned side, it's controlled. The difference in density is obvious without measuring anything.

Why it hit goldenrod so hard

I'm going to take a swing at explaining this, but fair warning: I'm not a botanist. I'm a guy who reads a lot and burns his own ground. Somebody who actually studies this for a living could probably tighten up what follows, and I'd welcome it.

Here's what I think is going on, and it's not about heat. It's about catching the plant at a bad moment.

It's broke when you burn it. Goldenrod comes up early and by June it's put everything it had stored in the roots into building stem. That's the low point in its year, energy-wise. You burn off the shoot it just spent all that on and it has to start over out of an account that's already close to empty.

Its growing point is sitting up where the fire is. This is the one that made it click for me. Goldenrod's growing tip is at the top of the stem, right out in the open. Grass keeps its growing point down at the crown or below, under the soil. So the same fire that just brushes past a grass plant takes the top clean off the goldenrod. Same flame, totally different result, and the only difference is where the plant keeps the part that matters.

It has to grow back into July. Whatever comes up after has to fight heat and dry soil, and by then anything else out there is going full tilt. It never really gets a good run at it.

Not much season left to restock. It's got less time to put energy back in the roots before things shut down for winter, so it comes up thinner the next spring. That's the part I think actually adds up. One burn stresses it. I don't think one burn fixes it.

The brome caught it too. This is why June 14th looked good on this spot in particular. Smooth brome is a cool season grass, so by mid-June it's already headed out and spent itself down on seed — same kind of vulnerable spot goldenrod is in. So one trip is working on both problems. Great on a brome pasture. Bad news if you had cool season stuff out there you wanted to keep. I got a little lucky on that count — the only good sedges anywhere near this section were down in a waterway, and it was wet and green enough that it never carried fire. They came through untouched. Worth knowing where your good stuff sits before you light anything, though. Low wet ground tends to take care of itself, but I wouldn't want to be counting on that.

The unit isn't sterile, for what it's worth — there was a butterfly working a thistle inside the burn while I was standing there. Fire is a disturbance, not a scorched earth event.

The unburned pockets make sense to me for the same reason, incidentally. Thick goldenrod shades out the fine fuel underneath it, and its own dead stems are coarse and don't carry fire like grass thatch does. The heaviest patches kind of protect themselves.

Why I'm messing with this at all

Somewhere in Iowa in June of 1820, prairie was burning. Had to have been. Fire out here wasn't a scheduled thing — it was a spark meeting dry fuel whenever that happened to line up, from lightning and from people who had their own reasons for lighting it and their own sense of when.

I don't want to push that further than it goes. From what I've read, most of the burning anybody documented on tallgrass prairie was fall and early spring, when the fuel is cured and fire moves easy. June wasn't the normal month. But it happened, and to me that's the useful part — there was variety in when this stuff burned. It wasn't one window every year.

And now it basically is. Most of us burn about six weeks in March and April. There are good reasons for that — it's safer, the weather cooperates, and it's what you can get permitted. But it's still a pattern, and a pretty narrow one. If you hit the same six weeks for twenty years straight, seems to me you're just picking out whatever handles those six weeks. Sometimes that's the exact thing you've been fighting.

So I'm always looking for other ways to disturb ground. Different timing, different intensity, different tools. Not because mixing it up is automatically good, but because I don't trust doing the same thing over and over and expecting it to keep working.

That said — I try to keep everything in mind on this stuff. Wildlife and insects aren't an afterthought for me, they're most of the reason I'm doing any of it. A June burn costs something to whatever's living out there at that moment, and "it used to happen naturally" isn't a free pass. Back then it happened across country where things had somewhere else to go. My two acres sit in a county that's mostly corn and beans, and the birds and bugs on that hillside don't have the options theirs did. That's a big part of why this was two acres and not two hundred, and why I'm fine with those unburned pockets staying right where they are.

What it costs you

The same thing that makes this work is what makes it expensive. Fire in May and June lands on a system that's fully awake, and goldenrod isn't the only thing with its growing point in the air.

Native forbs take the hit too. Anything that's bolted is vulnerable by the same mechanism. On a degraded unit that's already gone to goldenrod monoculture, there isn't much to lose — that's exactly the situation where this tool makes sense. On a diverse remnant, it's a different calculation entirely, and repeated late spring burns will flatten your forb component and push you toward grass.

You're inside nesting season. May and June is peak grassland bird nesting in the Midwest. A burn then destroys active nests. That's a real cost and it should be a deliberate decision, not something you find out about afterward.

Insects don't relocate. Burning growing-season habitat kills invertebrates that would have overwintered or dispersed. This is where those unburned pockets stop being a failure and start being the point — leave refugia on purpose, don't burn the whole property in one year, and give things somewhere to recolonize from.

None of that is a reason not to do it. It's a reason to be specific about where you do it and why.

The part people skip: have a plan for the back end

This is the piece I'd underline.

Do not go burning late and leave it at that.

A late burn opens ground up. You've knocked back the dominant plant and created bare soil and light in the middle of the growing season, when there isn't much standing to fill it. Something is going to occupy that space. If you don't decide what, the seed bank and whatever's nearby will decide for you — and in a lot of these situations that means the goldenrod comes right back, or you trade it for something worse.

This particular area is getting broadcast seeded with a high density native ecotype mix. That's the follow-up. The burn creates the opening; the seed determines what fills it. High density matters here — you're trying to occupy the ground fast enough that the goldenrod doesn't reclaim it, and a thin rate just gives it room to work with.

If you're considering this approach, work backward:

  • Have your seed in hand before you light anything. Sourcing a good local ecotype mix takes lead time. Don't burn and then start shopping.
  • Think through your seeding timing. Most native forbs need cold stratification, so seed going down behind a June burn is largely going to sit until the following spring regardless. Plan for that rather than being surprised by a quiet first summer.
  • Match the mix to the site. Soil, moisture, and shade from the adjacent timber matter more than the species list that looks good on paper.
  • Expect to come back. Goldenrod surviving in unburned pockets is a live source for re-invasion. Year two and year three are part of the plan, not a contingency.
  • Know your fire plan. Growing season conditions are not spring conditions. Fuels, humidity, wind, greenness, and neighbors all behave differently in May and June than they do in March.

The takeaway

If goldenrod has become the dominant forb on a brome pasture or a genuine problem area, a late season spring burn belongs in the toolbox. It works — you can see it in the difference across the line here.

But two acres is two acres. This is one hillside, one burn, one season, and I'll know a lot more about it next June than I do now. Run your own small test before you scale it, and run it somewhere you can afford the answer to be no.

And it's a tool, not a solution. The burn is the opening move. What you put in the ground behind it is what determines whether you've solved the problem or just rearranged it.