You can't (as far as I know - but I do get lost in the forest fixating on the trees sometimes
🙂The sponsored junk, ads, and all the other garbage can be removed easily with Adblock Plus, and/or JavaScript and/or CSS which is what I do. I have a few thousand lines of code/rules in Stylish (CSS rules), Adblock Plus (element hiding rules), and GreaseMonkey (element hiding engine I wrote) that make the eBay pages not annoy me so much by moving or totally removing things.
I'm going to ramble here based on assuming use of Firefox browser. If using Chrome, most of this is also doable. If Edge or IE you are out of luck, if Opera or Safari, probably out of luck.
A couple of Adblock Plus element hiding rules would do the trick, but
1) those rules would always remove the Sponsored links unless the rules are disabled except when wanting to print a listing (I know you normally want to see the %#&$&#$^ things
🙂2) requires installing AdblockPlus
Newer version of Adblock Plus have an element hiding helper optional addon that provides point and hide capability so you don't have to use Firebug and manually inspect the page code to create a rule)
https://adblockplus.org/elemhidehelperThe Stylish addon in Firefox with CSS rules does the same thing as the Adblock Plus element hiding rules, but more elegantly, with more options, and more specificity (if needed). But require manual rule writing.
My GreaseMonkey JavaScript approach does the same thing as the above, basically replicates Adblock element hiding rules, but with less specificity. It was the first approach I took to the problem years ago, and I'm too lazy to convert the rules to Stylish or Adblock Plus, so I just let it run.
It would also be possible to hardcode a set of basic CSS rules into a Firefox usercontent.css file that would do the same thing the Stylish addon does (but without a GUI editor or the ability to disable the rules without shutting down Firefox and editing the usercontent.css file again). It's an ok approach for universal rules that can just always run like modification to browser chrome (widen the browser google search bar, etc), but not as much for site specific rules that might require changes or disabling often. The Chrome browser can no longer use this approach.
A viable possibility would be the GreaseMonkey JavaScript approach but through the use of a bookmarklet (not requiring any addons). The bookmarklet would contain a bit of JavaScript along with hardcoded, embedded CSS/element attribute rules, and would be used as needed. ie: You are on the listing page you want to print, but there are sponsored listings, eBay recommendations, and other junk you don't want to print. Click the bookmarklet on the toolbar, and it would hide the (hardcoded, predefined) offending elements. Print the page. If page is reloaded, the hidden elements will re-appear (the GreaseMonkey, Stylish, and Adblock Plus approaches hide the elements every time the page loads unless disabled, while the bookmarklet approach just operates on the already loaded page and fixes it up)
Another way is to manually edit the pages/DOM, using built in Web Developer in Firefox, or addons like Firebug, Lola, or dozens of other available HTML editing tools. (most of these require a working knowledge of HTML and CSS.
A more element oriented Firefox addon tool is called PrintEdit. It hangs out on the Firefox toolbar, and when on a page if the icon is clicked, pulls up a modified print preview that can be toggled to an edit mode. In edit mode, as you mouse over elements they are highlighted with red borders. Click on a highlighted element and it is selected. Hit the delete key and it goes bye-bye. When all the junk is deleted switch back to preview and print. Also has some more advanced CSS functions. An awesome tool. Reload the page and all is as it was.
None of that solves your immediate problem, but shows some ways what you are asking can be done. Adblock Plus or PrintEdit are probably the easiest.
If you decide to venture down one of those paths, ask if you need help with the tools or rules for specific eBay page elements, etc.
(I'm going to think about the bookmarklet approach when I get some time - I believe something fairly/somewhat universal might be doable in 50 lines of code, maybe....)
