Two SQL servers for one website
Load balancing writes in SQL Server is hard. Are you sure this is actually a requirement? If not, and the servers just ended up this way because the implementers didn't understand the requirement, I would start with a single copy of the database that both web applications use, instead of trying to give each database an independent copy.

If it really is the requirement, then you could look into Distributed Partitioned Views, Peer-to-Peer Replication, Bidirectional Replication, or Merge Replication, all of which allow you to combine writes or otherwise share data from multiple instances. My guess, though, is that these solutions are overkill for your actual business requirements.