Search data
Search engines keep only a limited stretch of your history, and their reports leave a lot out. This pipeline stores everything still available in your own database and keeps it current, so you can see how a change to your site affected the way people find it. It suits any business that depends on being found online.
Tools Python · PostgreSQL · Flask · Search Console · Google Analytics · Claude
Built for AngelFire Ammunition
A Kansas ammunition manufacturer in Saint Marys.
The problem
Search performance was checked by exporting reports by hand. The exports were capped, so many searches never showed, and the search provider deletes older history, so the past was disappearing.
What I did
I built a pipeline that moves all the search history still available into the company's own database and keeps it current, with a dashboard and a weekly report. If a pull fails, an alert goes out.
The result
The company keeps its own search history, and nobody exports and stitches reports together by hand. After a site change, its effect on search can be checked against that history. The data set the direction: effort goes to the niches the site can win, rather than broad searches it cannot win yet.