Personally, I would be inclined not to store it in the database at all, but rather create a background task to pull out the site, analyze it and filter it using the read port, and then save it to the file system somewhere (public or non, public, in depending on your needs, you can easily write an asset controller to publish non-public static content) using a directory scheme that uniquely identifies it.
, - , , , , - , , .
- , URL-, - , , ( , ), / , , .